MCP server: simcrux mcp
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
Research direction
This is design work, not a starter task: the first tool set is explicitly open for debate and the payload names no existing code path to start from. Before any implementation, a maintainer needs to settle the tool list, the Pro gate behaviour and the simcrux://open?... citation format. Done would mean an agreed design and a scoped first milestone, such as a simcrux mcp stdio entry point with one read-only tool.
Written by the indexing model from the issue text.
Description
Coding agents (Claude Code, Copilot, Cursor, Codex) talk to tools over MCP. SimCrux has no MCP server, so an agent working on a design can use SimCrux only by driving its command line or reading files itself.
Request
An MCP server for SimCrux, started as simcrux mcp (stdio), that exposes the models SimCrux already builds:
A first tool set to argue with:
- run a regression from its config; the last results; one test's log and failure; the trend for a test; the formal results of a SymbiYosys or EQY project
- Pro: flake detection and the regression comparison
Rules:
- Few, small tools. Every tool definition is sent with every agent request whether it is called or not, and agents call plain queries with short descriptions. Keep the whole definition set small, and test its size.
- Same answers as the app. Each tool returns what the app or CLI would for the same input, from the same code path; nothing the app cannot do.
- Navigation free, analysis licensed. Tools that read and navigate are open core. Tools that run a Pro analysis honour the same tier gate as the app and say so in their result when the gate is closed.
- Citations a person can open. Anything a tool points at carries its coordinate (file and line; signal and time; cell or net) and, where the product has one, its
simcrux://open?...link, so the person reviewing the agent's answer can open the evidence in one click. - Local and confined. Paths resolve inside a root given at start; no network; nothing written into the user's tree unless a tool's name says it writes.
Why
An agent reads the design over MCP; a person checks what it found by opening the cited evidence in the app. The server is the first half of that, and the links are the second.
- Dominant language
- Dart
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Ferrite-Engineering/simcrux
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Check flow tools reports LibreLane and the PDK missing under the Nix launcher, though runs workOpen
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in Ferrite-Engineering/simcrux
Similar issues
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dreautall/waterfly-iii#890 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
fujidaiti/smooth_sheets#655 ·
Maintainers usually reply within 1 day