SpiceMCP
Related Servers
Alternatives to SpiceMCP
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceMCP server for automating LTspice on macOS, enabling simulation, schematic generation, data extraction, verification, and rendering via natural language or agents.7122-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables LLMs to read and modify LTspice schematics, run simulations, parse results, and generate plots, all through natural language.6-
- 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.48451 PyPI75GPL 3.0
- AlicenseBqualityDmaintenanceAn MCP server that connects LLM assistants to LTspice/ngspice circuit simulation, enabling design, verification, and iteration on schematics and netlists with structured numeric results.49GPL 3.0
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables agents to control LTspice on macOS for running simulations, generating schematics, extracting data, and automating verification workflows.MIT
- AlicenseAqualityDmaintenanceMCP server for Micro-Cap 12 SPICE simulator enabling LLM agents to run analog circuit simulations, including analyses, sweeps, and retrieval of curve data and plots.205MIT
TDQS
Scored across 14 tools
Most tools target distinct workflow stages (feasibility, template start, optimization, evaluation, querying, finishing, reporting, rendering). The only real ambiguity is among the simulation family—simulate vs evaluate_candidate vs run_optimization—but descriptions explicitly distinguish one-off/no-save from in-run/cached vs let-server-search. check_feasibility also overlaps slightly with start_optimization's refusal logic, though it's framed as a free pre-check.
Nearly all names are snake_case with clear verb_noun or verb_object structure (check_setup, generate_design_report, start_optimization, evaluate_candidate, rollback_to_candidate). The one deviation is the bare verb 'simulate' with no noun, and 'finish_design' vs 'start_optimization' use slightly different framing, but overall the convention is predictable.
14 tools sit comfortably in the well-scoped 3-15 range. Each tool earns its place across the circuit-design lifecycle (setup, feasibility, templates, parts, simulate, optimize, evaluate, query, rollback, finish, report, render) with little apparent redundancy.
The surface covers a full design lifecycle: environment check, feasibility, template discovery, part lookup, simulation, optimization run creation, candidate evaluation, run querying, rollback, standard-value finishing, reporting, and schematic rendering. No obvious dead ends remain for the stated circuit-design purpose.