ltspice-mcp vs MagicON RF Design Engines
ltspice-mcp is a plugin bundle for AI coding tools published by cognitohazard. Marketplaces we read that list it: 2 (Community GitHub marketplaces, PyPI (MCP servers)). MagicON RF Design Engines is an MCP server published by magiccadai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ltspice-mcp |  MagicON RF Design Engines |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.8.0 Downloads/month (PyPI): 1 151 Downloads/week (PyPI): 336 Forks (GitHub): 8 Stars (GitHub): 70 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ltspice-mcp | MagicON RF Design Engines |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 70 | No figure on GitHub |
| Forks (GitHub) (differs) | 8 | No figure on GitHub |
| Last release (differs) | 2026-11-07 | Not published |
| Where it runs (differs) | On your machine (ltspice-mcp) | Remote server (api.pcbgenerator.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | GPL-3.0-or-later | Not stated |
| Repository (differs) | github.com/cognitohazard/ltspice-mcp | Not stated |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 27 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ltspice-mcp
MCP tools for LTspice/ngspice circuit simulation and LTspice .asc schematic editing. Structured results include per-device operating points (gm/gds/vth) by device name, without parsing raw files. Requires uv and a simulator (LTspice or ngspice) on the host; the server is fetched from PyPI via uvx on first use.
MagicON RF Design Engines
TX/RX/T-R chains, OTA link, radar, PCB filters, patch antennas, stackup, thermal, PDN, compliance.
How to run each
ltspice-mcp As a Claude Code plugin
/plugin marketplace add cognitohazard/ltspice-mcp
/plugin install ltspice-mcp@ltspice-mcpMagicON RF Design Engines As a remote MCP server
claude mcp add --transport http magicon https://api.pcbgenerator.com/mcp/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only MagicON RF Design Engines has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ltspice-mcp · What it can do: MagicON RF Design Engines · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.