Skip to main content
Glama
Suzu-Gears

circuitjs-mcp

by Suzu-Gears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to circuitjs-mcp

No user-submitted related servers found.

    Related Servers

    • ltagent-mcp

      AbiyuLingga
      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

    • qucs-mcp

      leonardoAB1
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP-compatible agents to generate Qucs circuit schematics, run simulations, and parse results programmatically.
      1
      MIT

    • circuit-sim-mcp

      ghensley
      F
      license
      Not graded
      quality
      F
      maintenance
      Provides circuit simulation capabilities via MCP, enabling creation, simulation (DC, AC, transient), and analysis of electronic circuits using PySpice.
      1
      -

    • crocodile-mcp

      aaldersondev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and decode, generate from scratch, and reset Crocodile Physics 1.7 circuit files (.cyp) without opening the GUI, exposing components, wires, electrical nodes and saved voltages and currents as MCP tools. Generated circuits open and simulate directly in Crocodile, and the whole format is exposed byte by byte.
      MIT

    • circuitsnap

      gambhirsharma
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables building and simulating electronic circuits by converting netlist descriptions or drawings into live CircuitJS1 simulation URLs.
      2
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: loading/exporting circuits, reading state, controlling simulation, running transient probes, taking screenshots, generating links, and escaping to JS. circuit_state and run_transient are separated clearly as snapshot vs. time-series sampling.

    Naming Consistency3/5

    Four tools use the circuit_ prefix, while sim_control, run_transient, screenshot, and eval_js follow different patterns. The names are still readable, but the convention is not uniformly applied across the server.

    Tool Count5/5

    Eight tools is a well-scoped count for a circuit simulator server. Each tool maps to a meaningful user need without redundancy or bloat.

    Completeness5/5

    The set covers the full simulation workflow: load, export, inspect, control, run transient analysis, capture output, and share. eval_js provides an escape hatch for anything not explicitly exposed, leaving no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources