# Reported issues for Circuitarium MCP Pod holds 10 of 10 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [Circuitarium MCP](/mcp/circuitarium-mcp). ## Most discussed ### RFC: add a Logisim Evolution 4.1 adapter with headless verification ## Why Logisim Evolution is a strong second adapter: its `.circ` project is XML and the official application exposes headless test-vector and TTY verification. Implementing it behind Circuitarium’s neutral contract will test whether the architecture is genuinely simulator-neutral. ## Proposed first milestone - Detect a user-supplied Logisim Evolution 4.1 JAR and Java 21+ without redistributing either. - Discover and inspect `.circ` projects. - Project circuits into the neutral IR with unknown [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/10) · 2026-07-26 · closed · 1 comment ### Add MCP Prompts for design review, comparison, and cross-model handoff ## Why Different model hosts should receive the same safe workflow guidance without Circuitarium becoming vendor-specific. MCP Prompts can package reliable starter workflows while leaving the user and host model in control. ## Proposed prompts - Review a circuit design using capabilities → inspect → netlist → ERC. - Compare a controlled baseline/candidate pair with both digest guards. - Create a cross-model handoff containing project reference, digest, profile, inference mode, findings, and u [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/7) · 2026-07-26 · closed · 1 comment ### Expose MCP Resources for catalogs, compatibility profiles, and synthetic examples ## Why The current tools are strong for active analysis, but static reference data should not consume tool calls or be repeated in every result. MCP Resources are a better fit for component catalogs, compatibility profiles, schemas, and synthetic examples. ## Proposed scope Add bounded, read-only resource discovery and reads for URIs such as: - `circuitarium://capabilities` - `circuitarium://profiles/crumb.unity/1.3.5` - `circuitarium://catalogs/crumb.unity/1.3.5/components` - `circuitarium: [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/6) · 2026-07-26 · closed · 1 comment ### Good first issue: verify one real MCP host with the published package ## Why this is useful Circuitarium ships copyable configurations for several MCP hosts and executable checks for the configuration shapes. A sanitized report from one real host gives new users stronger evidence about the last mile from installation to `tools/list` without turning one vendor into the project contract. ## Bounded scope Choose **one** host currently documented in `docs/client-setup.md` (Codex, Claude Code/Desktop, VS Code, LM Studio, or Jan) and verify the published `circuitariu [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/28) · 2026-07-29 · open · 0 comments ### Good first issue: add a source-cited Logisim Probe component profile ## Why this is useful The 4.1.0 standard-library catalog names 169 built-in identities, while the curated neutral profiles intentionally cover only components whose behavior and ports have been source-cited. A single additional profile is a useful, reviewable contribution that improves model guidance without widening the simulator contract. ## Bounded scope Add one neutral profile for Logisim-evolution 4.1.0's **Wiring / Probe** component in `src/domain/componentProfiles.ts`. The profile sho [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/27) · 2026-07-29 · open · 0 comments ### Build a golden cross-model MCP evaluation suite ## Why Circuitarium is intentionally model-neutral, but schemas that work for one frontier model can still confuse another model or a smaller local model. A reproducible evaluation suite should measure task success without checking proprietary designs into the repository. ## Proposed scope Create synthetic scenarios for: - capability discovery and project selection - component lookup, BOM, netlist, and ERC - clean vs failed vs inconclusive interpretation - digest conflict recovery - baseline [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/12) · 2026-07-26 · open · 0 comments ### Specify conversion-loss reports for cross-adapter import and export ## Why CRUMB, Logisim, HDL, SPICE, and future backends model different concepts. Conversion must never force unsupported semantics into the destination or hide what was dropped, approximated, renamed, or left unresolved. ## Proposed scope Define a versioned loss report consumed by future `export.design` and `export.translate` workflows. Each entry should identify: - source entity and stable ID - destination capability or entity, when any - disposition (`preserved`, `approximated`, `dropped` [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/11) · 2026-07-26 · open · 0 comments ### CRUMBLE: add digest-guarded new-file-only crumb_apply_edit ## Why Once `crumb_plan_edit` has passed its evidence gates, Circuitarium needs a narrowly constrained apply operation that preserves unknown bytes and cannot silently mutate the wrong revision or overwrite a user’s design. ## Required safety contract - Require the source digest and plan digest. - Permit only a new workspace-contained `.cru` destination. - Refuse existing destinations, symlink/junction escapes, stale plans, ambiguous spans, and unsupported operations. - Apply minimal non-over [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/9) · 2026-07-26 · open · 0 comments ## Most recent ### CRUMBLE: expose a guarded crumb_plan_edit preview tool ## Why The private byte-preserving round-trip layer can support a safe public write arc only after operations are evidence-backed. Planning must remain separate from applying so a user/model can inspect exact intent, unsupported fields, and expected findings before any file is created. ## Proposed scope Start with the smallest operations that pass controlled CRUMB 1.3.5 reopen/resave evidence (for example rename, one typed scalar, move, or removal). The tool must not write. ## Acceptance cri [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/8) · 2026-07-26 · open · 0 comments ### Define the Circuitarium portable project and neutral netlist IR v0.1 ## Why Circuitarium currently has a neutral MCP envelope, but the richest design model is still CRUMBLE/CRUMB-specific. A versioned portable intermediate representation is the foundation for adding Logisim, conversion, simulation, and cross-adapter comparison without making one simulator’s format the source of truth. ## Proposed scope - Define stable IDs for projects, hierarchical components, ports, nets, buses, parameters, and adapter evidence. - Represent firmware and other sensitive payloa [Read the thread](https://github.com/Craftiee/circuitarium-mcp/issues/5) · 2026-07-26 · open · 0 comments The remaining reports are on [the project's issue tracker](https://github.com/Craftiee/circuitarium-mcp/issues).