Skip to main content
Glama
xuio

ltspice-mcp

by xuio
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

      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
      41
      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
      1
      MIT

    • SpiceMCP

      oniondas
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for LTspice circuit simulation and optimization. It manages optimization state, evaluates metrics from .meas directives, and supports schematic generation and parameter tuning.
      5
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 71 tools

    Disambiguation2/5

    Many tools have overlapping purposes, such as multiple ways to create a schematic (createSchematic, createSchematicFromNetlist, createSchematicFromTemplate, createIntentCircuit) and multiple simulation entry points (simulateNetlist, simulateNetlistFile, simulateSchematicFile, runSimulation, queueSimulationJob). Despite detailed descriptions, the high number of similar tools hinders clear disambiguation for an agent.

    Naming Consistency4/5

    Tool names follow a consistent camelCase verb_noun pattern (e.g., getBandwidth, createSchematic, listJobs). There are minor deviations like 'daemonDoctor' and 'autoCleanSchematicLayout', but overall the naming is predictable and consistent.

    Tool Count2/5

    With 71 tools, the server is heavily overloaded. For a domain like circuit simulation, 10-20 tools would be well-scoped. The excessive number implies redundancy and complexity, making it cumbersome for agents to navigate.

    Completeness4/5

    The tool set covers a wide range of tasks: schematic creation, simulation execution, result analysis, job management, UI interaction, and telemetry. There are minor gaps (e.g., lack of a direct 'delete schematic' tool), but overall it is quite complete for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week

    Resources