MCP server: simcrux mcp

オープン
#46 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
ai-infra-agents, dart
領域
ai, cli

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Dart
スター
0
フォーク
0
平均マージ
2日 10時間
マージ済み PR(30日)
3

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Ferrite-Engineering/simcrux のほかの issue

Ferrite-Engineering/simcrux の issue をすべて見る

似ている issue

Dart の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。