Skip to main content
Glama
mcp-spice
by zesun33

Related Servers

Alternatives to mcp-spice

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A thin MCP server that wraps spicelib for circuit simulation. Exposes tools for running AC, transient, DC op, and parameter sweep analyses, enabling behavioral model fitting through iterative simulation and measurement comparison.
      4
      8
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Generates, simulates, and inspects LTspice circuits via MCP tools and resources, providing structured JSON interfaces for AI agents.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to generate Qucs circuit schematics, run simulations, and parse results programmatically.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables building, saving, inspecting, and previewing supported circuits, plus running headless harmonic-balance simulations and comparing parameter variants without using the desktop UI.
      21
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables debugging LTspice circuits through natural language by exposing netlists as structured text, including components, nodes, directives, static checks, and simulation logs, so LLMs can reason over circuit topology instead of screenshots.
      -
    • A
      license
      C
      quality
      C
      maintenance
      Enables an assistant to edit .asc schematics, run the simulator, and read logs and waveforms through stable JSON tools.
      145
      11
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    spice_run executes a simulation and returns results, while spice_toolchain_info reports environment/version details. Their purposes are completely distinct with no functional overlap.

    Naming Consistency4/5

    Both tools share the spice_ prefix and snake_case style, but spice_run uses a verb while spice_toolchain_info is more noun-like. This is a minor inconsistency rather than a chaotic naming scheme.

    Tool Count4/5

    With only two tools, the set is slightly below the typical 3-15 range, but it is still reasonable for a narrowly focused SPICE execution server. The small count matches the minimal scope.

    Completeness4/5

    The server covers the core run-and-inspect workflow with parsed .meas results and log tail access. It lacks raw output or full-log retrieval, but these are not obvious dead ends for the intended simple simulation use case.