Circuitarium MCP server

by Craftiee·io.github.Craftiee/circuitarium·v0.3.1·1 stars

No reviews yet

MCP tools for CRUMB artifacts and Logisim-evolution analysis and non-interactive simulation.

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

Growing

1 stars62 downloads/wk

Reviews

Write one

Nobody has reviewed Circuitarium MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Circuitarium MCP tools (22, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

crumb_analyze_design
Recognizes version-pinned component parameters, terminal attachments, and inferred connection groups. Summary is the bounded default; components and connections use opaque cursors. Embedded firmware and geometry require explicit opt-in.
crumb_bom
Groups recognized components by kind and decoded part values into quantities. State values such as switch positions are excluded from part identity; unknown and schema-mismatched components stay visible as their own lines.
crumb_check_design
Lints the inferred netlist: supply shorts, LEDs directly across the rails, shorted two-terminal parts, floating IC power pins, resistor power ratings, and floating terminals. Findings carry evidence confidence and rule basis; a rule violation returns ok=true with data.valid=false.
crumb_compare_designs
Read-only, GUID-matched comparison of a baseline and candidate .cru under crumb.unity/1.3.5. Distinguishes exact bytes, modeled equivalence, root changes, component changes, and unverified payload signatures without returning raw XML, firmware, EEPROM bytes, or thumbnails.
crumb_component_catalog
Returns the version-pinned CRUMB tool-ID catalog, payload signatures, typed parameters, terminal labels, confidence values, and their machine-readable evidence vocabulary. Optionally filter by toolId.
crumb_export_netlist
Collapses jumper wires out of the inferred connection graph and returns paged electrical nets with component terminals, VCC/GND names inferred from DC supply terminals, and optional saved-switch-state merges. Provenance and confidence are explicit.
crumb_generate_fixturewrite action
Creates one known fixture without overwriting. Provide outputPath for a file artifact; raw XML is returned only when includeXml=true.
crumb_get_component
Returns a single component by id with parameters, terminals, geometry, its inferred connection groups, and windowed access to embedded firmware source past the analyze cap. The read-back companion for iterative work on one part.
crumb_ic_reference
Queries the version-pinned tool-5 IC registry by prefabId or by a label/package substring (for example "74HC138"). Returns package labels, ordered pin names, and explicit unresolved pins.
crumb_inspect_design
Returns a bounded save summary and tool-ID counts. Use crumb_analyze_design for paginated semantic component and connection details.
crumb_list_projects
Enumerates .cru files under the workspace root (or one subdirectory) with size, modification time, and SHA-256 digest, so a model can discover projects without being handed a path.
crumb_trace_net
Selects one component terminal by stable index and returns a paged deterministic connectivity witness with structured attachment, board, jumper, and optional saved-switch provenance. It is static conductive inference, not current flow, path enumeration, or simulation.
crumb_validate_design
Performs XML and CRUMB structural checks without launching the game. A bad design returns ok=true and data.valid=false.
electronics_capabilities
Zero-argument onboarding for model-neutral conventions, callable backends, truthful limitations, and recommended workflows. Call this first when unsure.
electronics_plan_verification
Builds a deterministic, simulator-neutral plan for explicit claims using bounded caller-reported evidence. It reads no files, runs no tools or simulators, authenticates no receipts, and never certifies physical hardware.
electronics_validate_experiment
Checks an arbitrary JSON value against the simulator-neutral circuit, firmware, probe, assertion, and timing contract. Invalid input returns ok=true and data.valid=false with diagnostics.
logisim_analyze_design
Parses bounded .circ XML into project, circuit, pin, clock, component, and explicit conversion-loss summaries. Static parsing is not simulation evidence.
logisim_component_stats
Invokes the separately installed JAR, after it self-reports Logisim-evolution 4.1.0, with --tty stats. Success proves that configured process loaded the staged project, not behavioral simulation or binary authenticity.
logisim_export_netlist
Exports simulator-neutral coordinate-endpoint nets with explicit loss markers. It does not infer unmodeled gate geometry, mid-segment junctions, or behavior.
logisim_list_projects
Discovers workspace .circ projects with stable raw-byte digests. This is static file discovery and does not launch Logisim.
logisim_run_test_vectorwrite action
Invokes the separately installed JAR, after it self-reports Logisim-evolution 4.1.0, with staged snapshots of a workspace-contained project and .vec/.txt file. Assertion failures return ok=true with data.valid=false.
logisim_truth_table
Invokes the separately installed JAR, after it self-reports Logisim-evolution 4.1.0, in CSV/binary table mode after statically bounding declared input width.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings

Code scan40 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 20 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Circuitarium MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 92/100; higher than 95% of 48,255 servers
Tools: 22; the typical server has 7
Tools that change things: 9%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 1; more than 65% of 28,688 servers
Downloads a week: 62; more than 50% of 12,191 servers with a package

What its tools let an agent do: 20 read · 2 change

Install Circuitarium MCP in Claude Code, Cursor or VS Code

Runs npx -y circuitarium-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add circuitarium -- npx -y circuitarium-mcp

Add to Cursor

What the publisher says

From the Circuitarium MCP repository's README, as published. We do not edit it. Read it on GitHub

Circuitarium MCP

Local electronics tools for MCP-capable assistants, with support for CRUMB save files and Logisim-evolution projects.

Circuitarium lets an MCP host inspect circuit files without pretending that static analysis is a running simulator. It can trace CRUMB nets, build BOMs, run electrical rule checks, analyze Logisim projects, and optionally ask Logisim-evolution to produce truth tables or run test vectors.

Release 0.3.1 includes 22 tools, nine read-only Resources, and four workflow Prompts. The server is model-neutral: Codex, Claude Code/Desktop, VS Code, LM Studio, Jan, or another local MCP host supplies the model and launches Circuitarium over stdio. Circuitarium itself needs no OpenAI, Anthropic, or local-model API key.

Quick start

You need:

access.

Node.js 22 or newer;
an MCP client that can launch a local stdio server; and
a dedicated folder containing only the circuit files you want the client to

Windows, macOS, and Linux are covered by CI. CRUMB analysis and the static Logisim tools need neither simulator nor Java.

To install and start the local stdio server from a terminal:

npx -y circuitarium-mcp@0.3.1

In an interactive terminal this prints a short status panel. In normal use, your MCP client runs the same command and keeps the server connected over stdio.

1. Add Circuitarium to your MCP client

Most clients ask for the same command, arguments, and environment variable:

Command: npx
Arguments: -y circuitarium-mcp@0.3.1
Environment:
  CIRCUITARIUM_MCP_ROOT=/absolute/path/to/circuit-workspace

The first launch can take longer while npm downloads the package. Later starts normally use npm's cache.

Replace the path with the smallest folder that should contain the .cru, .circ, .vec, and .txt files available to the model. Do not point it at your home directory or a drive root.

Copyable configurations are available for:

Codex
Claude Code
VS Code
LM Studio
Jan

See the client setup guide for platform-specific examples and local-model guidance. The starter workspace recipe copies one synthetic CRUMB fixture plus the full-adder Logisim project into an isolated folder, so a first test does not require access to the rest of a source checkout. Restart or reload the client after adding the server.

Claude Desktop users can instead download circuitarium-mcp-0.3.1.mcpb directly and open it as a local bundle. The installer asks for a circuit workspace and offers optional Logisim JAR and Java settings. The release page also includes checksums and the matching npm tarball.

2. Try a circuit with no simulator installed

Paste this into the connected client:

Use Circuitarium. Call electronics_capabilities. Create the built-in

breadboard-led fixture as demo/first-led.cru without overwriting

anything, analyze it, and run crumbcheckdesign. Explain which findings

are static inferences rather than simulation results.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Circuitarium MCP: common questions

Is Circuitarium MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the Circuitarium MCP safety report
How do I install Circuitarium MCP?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Circuitarium MCP need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Circuitarium MCP maintained?: The last commit was 60 days ago (2026-09-05). The latest release is v0.3.1.
How does Circuitarium MCP compare with other MCP servers?: safety score 92/100 (higher than 95% of 48,255 servers); tools 22 (the typical server has 7); tools that change things 9% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.