Skip to main content
Glama
clanker-lover

SPICEBridge

by clanker-lover
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to SPICEBridge

No user-submitted related servers found.

    Related Servers

    • ltspice-mcp

      ossenna-hq
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that connects LLM assistants to LTspice/ngspice circuit simulation, enabling design, verification, and iteration on schematics and netlists with structured numeric results.
      49
      GPL 3.0

    • ltspice-mcp

      Cognitohazard
      A
      license
      A
      quality
      B
      maintenance
      An 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.
      48
      208 PyPI
      45
      GPL 3.0

    • LTspice MCP Server

      luc-me
      F
      license
      C
      quality
      C
      maintenance
      This server enables LLMs to design, simulate, and debug electronic circuits using LTspice via natural language commands. It automates netlist generation, library component validation, and iterative error correction for SPICE simulations.
      2
      1
      -

    • microcap-mcp

      monoxide-xen
      A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      20
      15 PyPI
      2
      MIT

    • ltspice-mcp

      xuio
      F
      license
      C
      quality
      C
      maintenance
      MCP server for automating LTspice on macOS, enabling simulation, schematic generation, data extraction, verification, and rendering via natural language or agents.
      71
      19
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target distinct operations (specific analysis types, measurements, or actions). However, auto_design overlaps with the combined workflow of load_template, simulation, and compare_specs, which could cause ambiguity for an agent deciding between high-level and individual tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., create_circuit, run_ac_analysis). The only minor deviation is 'auto_design', but it still uses the same imperative style. Overall, naming is predictable and uniform.

    Tool Count4/5

    28 tools is moderately high for a single server, but the domain of circuit simulation and design justifies many distinct analysis, measurement, and management operations. The count is on the upper end of reasonable but not excessive, as each tool has a clear purpose.

    Completeness3/5

    The set covers core design, simulation, and measurement workflows. Notable gaps include the absence of a tool to list stored circuits (agents cannot enumerate existing circuits) and no tool to delete models or update models. These gaps may cause occasional failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources