MagicON RF Design Engines
io.github.magiccadai/magicon · v1.1.0
TX/RX/T-R chains, OTA link, radar, PCB filters, patch antennas, stackup, thermal, PDN, compliance.
MCPremoteno credentialsLaw & government
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 15 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 80/100
What it does: 15 tools · 15 read, 0 write
Test call design_rf_receiver: failed — tool error: {"ok": false, "error": "design_rf_receiver needs either explicit stages or an rfFrequencyHz to select parts for", "groun (1,140 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: 0
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://api.pcbgenerator.com/mcp/Tools
15 tools listed at last check
design_rf_chainDesign a complete RF transmitter chain with the convergent orchestrator: selects the driver, PA, filter, and connector (the signal source is the user's input power by default — no VCO unless one is explicitly the generator), matches drive power between stages, inserts a pre-driver or attenuator whendesign_rf_receiverDesign or analyse a superheterodyne RECEIVER. Selects catalog parts for each slot (limiter, LNA, image filter, mixer, LO, IF filter, IF amp, step attenuator) and returns the frequency plan (image, half-IF, LO leakage), the cascaded noise figure, noise floor, MDS, sensitivity, SFDR and dynamic range,design_tr_moduleDesign a T/R (transmit/receive) module that shares ONE antenna between a transmitter and a receiver. Designs both chains through the existing engines, selects the shared front end (a T/R switch, or a circulator with a receive-path limiter), and returns four safety budgets: TX-to-RX isolation againstrun_link_budgetCompute a cascaded RF link budget. For the chain just designed, call with NO arguments — the server derives stages and input power from the design. Pass stages + inputPowerDbm only for a bench/hypothetical chain. Returns per-stage output power, cumulative gain, Friis cascaded NF, gain-referred reciprun_stackup_solverRun the impedance-aware stackup constraint solver to find optimal PCB configurations. Use when the user wants ranked material/thickness/copper solutions for a given layer count and frequency. Returns scored and ranked feasible stackups. Each solution's prepreg_thickness_mm is ONE prepreg layer: preprun_thermal_analysisRun a full PCB thermal analysis: via array Rth, junction-to-ambient stack, Kennedy spreading, Coffin-Manson barrel stress, Timoshenko warpage, and resin-flow estimation. Mirrors POST /api/stackups/{id}/thermal-analysis. Call with no arguments once a design exists: the server takes power_w from the drun_pdn_analysisRun a PDN (power delivery network) impedance analysis: interplanar plane-pair capacitance, multi-cap decoupling impedance vs. target impedance, violations, and recommended decoupling caps. Reuses the Phase-25 engine behind POST /api/pdn/analyze. Inputs are derived server-side from the solved stackuprun_compliance_analysisAudit the solved stackup against PCB standards (IPC-2221, IPC-6012, IPC-4101, MIL, UL-94, RoHS, REACH): per-rule pass/fail with severities and remediation. Reuses the engine behind POST /api/compliance/check. Layers are derived from the solved stackup and standards default to IPC-2221 + IPC-6012 Clarun_ota_linkCompute a one-way over-the-air link budget — EIRP, free-space path loss (Friis), received power, link margin against receiver sensitivity, a closes/marginal/fails verdict, and the maximum range — using the SAME engine behind POST /api/ota-link/compute. Receiver sensitivity is reused from a prior linrun_radar_performanceCompute radar performance — the monostatic range equation (received power, SNR vs range, maximum detection range, coherent/non-coherent integration gain) and pulsed-waveform relations (duty cycle, unambiguous range/velocity, range resolution, blind speeds) — using the SAME engine behind POST /api/rarun_planar_filterSynthesize a passive planar (copper-on-PCB) filter from analytical formulas: stepped-impedance / open-stub low-pass, or parallel-coupled / hairpin band-pass, Chebyshev or Butterworth. Returns per-section line impedances (Z0e/Z0o for coupled sections), width/spacing, quarter-wave lengths, the total odesign_patch_antennaDesign a rectangular microstrip patch antenna (and, when both nx and ny are given, a uniform planar array of it) using the Balanis cavity/transmission-line + array-factor model — the SAME engine behind POST /api/antenna/patch/design and the Guided Phase IV antenna panel. The substrate (dk/df/h) derirun_glass_weave_analysisRecommend PCB glass-weave (fiber-weave) styles for the current design: ranks catalogued styles by impedance variation and cost for the design frequency and marks the cheapest one meeting the impedance tolerance. Reuses the Phase-24 engine behind POST /api/glass-weave/recommend. Frequency is derivedlookup_component_by_mpnLook up an RF component in the validated catalog by manufacturer part number: what its datasheet says, as our record states it. Returns the frequency, power and gain ranges, package, datasheet link, and the headline figures (Psat, P1dB, gain, noise figure, OIP3, insertion and conversion loss), eachcheck_groundingCheck a draft passage against the engine results computed in THIS session. It returns every figure no engine produced, and every claim it checks that the results do not support or contradict (for example a solver score called a loss), each in `findings` with the reason. Run it before publishing or h
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.magiccadai/magicon)