circuitarium-mcp
Related Servers
Alternatives to circuitarium-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server for working with Logisim-evolution .circ projects, providing structured project inspection, guarded edits, validation, circuit analysis, test execution, format conversion, and GUI launch.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to build Logisim circuits from natural language by adding pins, gates, LEDs and wires through tools that return exact port coordinates, then saving the result as a .circ file. It also runs Logisim's own loader to read the file back and report dangling wire ends and multi-driver shorts.MIT
- AlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools for parsing KiCad netlists and schematics, running evidence-based audits, and generating deterministic sizing and BOMs.MIT
- AlicenseBqualityCmaintenanceProvides schematic/PCB analysis, authoring, and SPICE simulation through MCP, enabling direct KiCad file manipulation and verification without requiring KiCad for reading.18MIT
- AlicenseNot gradedqualityCmaintenanceEnables inspection of existing KiCad boards and schematics — layer/component/net reading, native DRC and ERC, XML netlist generation, Gerber/Excellon export, and GND continuity auditing — plus running LTspice or ngspice simulations with RAW waveform summaries and CSV export. It checks existing designs and preserves artifacts and evidence rather than performing GUI editing, auto-placement, or auto-routing.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
TDQS
Scored across 22 tools
Every tool has a clearly distinct purpose, reinforced by consistent prefixes (crumb_, logisim_, electronics_) and explicit descriptions. Even closely related tools like crumb_validate_design (structural XML checks) and crumb_check_design (netlist linting) are unambiguously separated. Higher-level analysis tools (inspect vs analyze) are differentiated by summary vs paginated detail.
The naming is mostly consistent with a predictable pattern: prefixes for simulators, and parallel names for shared operations (list_projects, analyze_design, export_netlist). Minor deviations exist, such as noun-phrase names (crumb_bom, crumb_ic_reference, electronics_capabilities) versus verb-first names, but the overall structure remains readable and coherent.
At 22 tools, this exceeds the typical 3-15 range, but the count is justified by covering two distinct simulators (CRUMB and Logisim) plus a generic electronics validation layer. Each tool serves a unique function, and the number feels appropriate for the breadth of the domain.
The tool set provides comprehensive coverage for circuit analysis and validation: project discovery, design analysis, validation, netlist export, tracing, BOM generation, IC lookup, and simulation/test execution. Minor gaps exist, such as lack of design creation/editing tools, but these appear outside the server's stated analytical purpose.