MCP server: simcrux mcp

Aperta
#46 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ai-infra-agents, dart
Ambito
ai, cli

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Dart
Stelle
0
Fork
0
Merge medio
2g 10h
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Ferrite-Engineering/simcrux

Tutte le issue di Ferrite-Engineering/simcrux

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.