Circuitarium MCP

Name: Circuitarium MCP
Author: Craftiee

by Craftieeversion 0.3.1i★ –iRuns on your computer

Registry nameio.github.Craftiee/circuitarium

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "circuitarium": {
      "command": "npx",
      "args": [
        "-y",
        "circuitarium-mcp"
      ]
    }
  }
}

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "circuitarium": {
      "command": "npx",
      "args": [
        "-y",
        "circuitarium-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "circuitarium": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "circuitarium-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Craftiee, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18336 servers in this category
Published to the registry more recently than 17% of the other 18336 servers in this category
Basic checks equal to or better than 100% of the other 18336 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Circuitarium MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

NexusWindows

by pironjulien

Windows computer use in the background: desktop apps driven without your mouse or keyboard.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

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 access.

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 crumb_check_design. Explain which findings

are static inferences rather than simulation results.

Your client may ask you to approve creation of the synthetic file. The tool refuses to overwrite an existing path; on a repeat run, analyze the existing file or choose a new name.

A healthy connection creates a small synthetic file, recognizes its breadboard and LED, and reports two floating-terminal warnings. The fixture is independently authored and safe to redistribute; it is not a CRUMB asset.

3. Check the launcher from a terminal

These commands verify the published launcher without opening a server session:

npx -y circuitarium-mcp@0.3.1 --help

npx -y circuitarium-mcp@0.3.1 --version npx -y circuitarium-mcp@0.3.1 doctor --smoke

If the bare npx -y circuitarium-mcp@0.3.1 command appears to wait, the server is working as designed: it is waiting for an MCP host on stdin. Press Ctrl+C and let the host launch the command itself.

Watch the terminal demo to see the source-checkout command runner inspect a synthetic fixture, build its BOM, and export its netlist. The public package exposes the MCP server, help, version, and doctor commands shown above.

Watch the MCP Inspector demo to see the server running in an independent MCP client, or read the reproducible 22-tool host verification and its sanitized evidence report.

What you can do

Area	Current capabilities
General electronics	Discover available backends, validate portable experiment descriptions, and plan what evidence is needed to verify circuit claims
CRUMBLE / CRUMB	Discover, inspect, validate, and compare Unity-era `.cru` saves; build BOMs and netlists; trace conductive nets; query supported IC pinouts; and run static electrical checks
Logisim-evolution	Discover and inspect `.circ` projects, export a deliberately partial neutral netlist, and optionally run component statistics, truth tables, and test vectors
Cross-model work	Preserve workspace-relative project references and raw-byte SHA-256 digests so another model can confirm it is reading the same artifact

CRUMBLE—Circuit Representation & Universal Model Bridge for Laboratory Electronics—is the unofficial CRUMB-specific integration inside Circuitarium. The simulator-neutral tools keep CRUMB-specific assumptions out of future adapters.

The current surface breaks down into three neutral electronics_* tools, thirteen crumb_* tools, and six logisim_* tools. All tool results use the electronics.mcp/0.2 result contract, independent of the package version.

Static analysis versus runtime execution

Operation	Simulator or Java required?	What it establishes
All `crumb_*` tools	No	Facts inferred from a saved Unity-era `.cru` file; never live CRUMB behavior
`logisim_list_projects`, `logisim_analyze_design`, `logisim_export_netlist`	No	Saved `.circ` structure and an explicitly partial neutral representation
`logisim_component_stats`	Java 21 and a user-supplied Logisim 4.1.0 all-JAR	The selected project and circuit loaded in one bounded subprocess
`logisim_truth_table`, `logisim_run_test_vector`	Java 21 and a user-supplied Logisim 4.1.0 all-JAR	Bounded behavioral evidence for the exact project digest; not a live GUI session
Resources and Prompts	No	Guidance and workflow templates only; they do not read a project or execute a simulator

Compatibility and honest limits

Target	Status	Boundary
CRUMB 1.3.5, Unity-era `.cru` format	Experimental support	Static, version-pinned file analysis under `crumb.unity/1.3.5`
Godot-era CRUMB 2.x	Not supported	Requires a separate evidence profile and controlled-save corpus
Live CRUMB control or simulation	Not implemented	No run, pause, step, signal-read, or GUI bridge
Arbitrary CRUMB editing	Not implemented	The only public write tool creates one of five fixed synthetic fixtures
Logisim-evolution 4.1.0 static analysis	Experimental support	Clean-room `.circ` parsing; neutral netlists remain explicitly partial
Logisim-evolution 4.1.0 execution	Optional	Bounded, one-shot JAR subprocesses; no live GUI session

CRUMB electrical rule checks operate on inferred net connectivity and saved component values. They can find supply shorts, an LED placed directly across both rails of one recognized supply, a directly connected resistor whose saved values imply excessive dissipation, and selected floating terminals or IC power pins. They do not trace series paths, prove polarity, calculate general circuit behavior, or certify a physical build.

[!WARNING]

Circuitarium is experimental educational software, not a safety

certification tool. Do not rely on its output alone for mains voltage,

battery charging, medical, automotive, life-safety, high-energy, or

regulatory work. Use authoritative component documentation, appropriate

measurements, and qualified engineering review wherever consequences

matter.

File parsing happens locally, but the MCP host may send returned data to a cloud model. Embedded firmware source is omitted by default, and binary EEPROM contents are never returned, but you should still use a narrow workspace with no secrets. Read the security policy for the full trust model.

Optional Logisim runtime

The three static Logisim tools work without Java. To enable component statistics, truth tables, and test vectors:

Install Java 21 or newer.
Download the official logisim-evolution-4.1.0-all.jar.
Add the JAR path to the MCP host configuration.

CIRCUITARIUM_LOGISIM_JAR=/absolute/path/to/logisim-evolution-4.1.0-all.jar

CIRCUITARIUM_JAVA=java

CIRCUITARIUM_JAVA is optional when java already resolves to Java 21 or newer. On a headless Linux machine, test-vector execution also needs a working X11 display; Xvfb is sufficient.

Use only a trusted JAR. Circuitarium verifies that it self-reports version 4.1.0, but that response does not authenticate the file or its publisher. Runtime tools may update Logisim's per-user Java preferences and are not an operating-system sandbox.

The repository includes an independently authored full-adder project and vector for a first runtime test. Circuitarium does not bundle or download Logisim-evolution. See the Logisim adapter guide for setup, Linux notes, evidence levels, and subprocess safeguards.

Typical workflows

Review a CRUMB save

Call electronics_capabilities.
Call crumb_list_projects if the path is not known. Projects include a digest when requested and within the documented file and aggregate bounds; otherwise the result explains why it was omitted.
Call crumb_analyze_design with view: "summary".
Use crumb_export_netlist, crumb_trace_net, crumb_check_design, or crumb_bom only as the question requires.

Static findings remain file-format inference. Circuitarium does not observe whether CRUMB is running or how the circuit behaves.

Verify a Logisim project

Call logisim_list_projects, then logisim_analyze_design.
Treat logisim_export_netlist as partial static evidence and review its conversion-loss markers.
If the optional runtime is available, select an exact circuit and call logisim_truth_table or logisim_run_test_vector.
Use electronics_plan_verification when a claim needs several kinds of evidence or an explicit list of remaining gaps.

Hand work to another model

Keep projectRef, projectDigest, backendId, adapterVersion, and compatibilityProfile with the handoff. The receiving model should pass the recorded digest as expectedProjectDigest on its

Only the beginning is shown; read the rest in the repo

Circuitarium MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

NexusWindows

README from the maker

Circuitarium MCP

Quick start

1. Add Circuitarium to your MCP client

2. Try a circuit with no simulator installed

3. Check the launcher from a terminal

What you can do

Static analysis versus runtime execution

Compatibility and honest limits

Optional Logisim runtime

Typical workflows

Review a CRUMB save

Verify a Logisim project

Hand work to another model