LTspice MCP
Related Servers
Alternatives to LTspice MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to create, read, update, and validate editable analog/RF circuit schematic projects (including a five-transistor OTA template), wiring and moving components by pin name, running topology checks, exporting SVG or SPICE/Spectre netlists and normalized JSON, and opening the browser editor with a project loaded. It also exposes the component library's exact pins and defaults so drawings stay netlist-correct.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to perform Electronic Design Automation (EDA) tasks including Verilog synthesis, simulation, ASIC design flows, and waveform analysis through a unified interface.6ISC
- AlicenseNot gradedqualityDmaintenanceGenerates, simulates, and inspects LTspice circuits via MCP tools and resources, providing structured JSON interfaces for AI agents.MIT
- AlicenseNot gradedqualityAmaintenanceGives coding agents structured access to an EDA toolchain so they can lint, simulate, formally verify, synthesize, place and route, program a board and read its UART. Returns parsed results (errors with file and line, timing per clock, utilization, inferred memories, counterexample traces) instead of raw logs, closing the run-simulate-fix loop without copy-paste.71 PyPI13AGPL 3.0
- AlicenseAqualityBmaintenanceAn MCP server that connects LLM assistants to real circuit simulation: LTspice and ngspice, plus direct editing of LTspice .asc schematics. Simulation results come back as structured numbers so the assistant can design, verify, and iterate on circuits.48454 PyPI68GPL 3.0
- AlicenseAqualityBmaintenanceExposes Cadence EDA tools such as OrCAD Capture, Allegro PCB Designer, and PSpice to AI assistants, enabling them to browse PCB files, generate schematics and netlists, and run circuit simulations through a license-free, cross-platform interface.13MIT
TDQS
Scored across 145 tools
145 tools include many overlapping run/prepare/measure/export operations (e.g., run_simulation, submit_batch, submit_remote_simulation; prepare_ac vs add_instruction). While names are descriptive, an agent will struggle to choose the right tool for a given task.
All tool names use snake_case with a leading verb (add_, get_, list_, prepare_, run_, etc.), forming a consistent verb_noun pattern. No camelCase or mixed conventions.
145 tools is extreme for any MCP server, far exceeding the 50+ threshold for mismatch. Many tools are thin wrappers around specific SPICE directives or analysis types, bloating the surface.
The surface covers schematic editing, simulation setup, execution, batch/remote runs, analysis, and export comprehensively. Minor gaps exist, such as no direct schematic deletion or fully supported live GUI control, but core workflows are complete.