Skip to main content
Glama
Cognitohazard

ltspice-mcp

by Cognitohazard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ltspice-mcp

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

      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
      -

    • SPICEBridge

      clanker-lover
      A
      license
      B
      quality
      C
      maintenance
      AI-powered circuit design through simulation — an MCP server that gives language models direct access to SPICE circuit simulation via ngspice, enabling natural language circuit description and automated netlist generation, simulation, measurement, and spec verification.
      28
      36
      GPL 3.0

    • 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
    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

    A3.9/5.0

    Scored across 48 tools

    Disambiguation5/5

    Each tool targets a very specific circuit design or analysis task, with detailed descriptions that prevent overlap. For example, edge_metrics, periodic_metrics, and pulse_response each handle distinct transient phenomena. Even tools that might seem similar, like simulation_summary and measurement_stats, serve different purposes (overview vs. aggregated .MEAS results).

    Naming Consistency4/5

    Names follow a mostly consistent verb_noun pattern for actions (add_component, run_simulation) but analysis tools use varied suffixes (_metrics, _stats, _summary) or are single words (resonance). The mix is still readable and predictable, with only minor deviations from a uniform pattern.

    Tool Count2/5

    48 tools is well beyond the typical 3-15 for a well-scoped server, indicating possible redundancy or over-specification. While the LTspice domain is complex, many tools could be merged or streamlined without losing functionality, e.g., combining several metrics tools into a single configurable analysis tool.

    Completeness5/5

    The tool surface covers the entire LTspice workflow: schematic editing, netlist creation, simulation setup and execution, result analysis (transient, AC, sweeps, Monte Carlo), library management, and validation. There are no obvious gaps; advanced features like diffing circuits and tracing nets are included. The set feels complete for the domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources