trios-mcp

Rust Model Context Protocol server that wraps the tri and trios-igla CLIs from gHashTag/trios-trainer-igla.

Anchor: phi^2 + phi^-2 = 3 Companion to the TRAINER-IGLA-SOT mission (Gate-2 deadline: 2026-04-30 23:59 UTC). Tracking issue: trios-mcp#1 · Cross-ref: trios-trainer-igla#35

Why

tri (Railway deploy + local train) and trios-igla (read-only ledger query) are the canonical operator surface for the TRAINER-IGLA-SOT pipeline. Today every agent shells out manually, parses free-form text, and reinvents the R7 triplet contract in its prompt. That is fragile and silently bypasses R5/R7/R9.

trios-mcp exposes every command as a typed MCP tool over stdio. The JSON-RPC layer never reinterprets CLI output:

• exit_code, stdout, stderr are forwarded byte-for-byte (R5)
• the R7 triplet stays a property of the wrapped binary (R7)
• igla_check is wired straight to the embargo predicate (R9)

Build

cargo build --release
# binary: ./target/release/trios-mcp

Tool catalog (15)

Mirrors trios-trainer-igla README §Commands 1:1.

tri deploy

Tool	Wraps
tri_deploy_init	tri deploy init
tri_deploy_seed	tri deploy seed --seed <N> [--steps --hidden --lr --attn-layers]
tri_deploy_all	tri deploy all
tri_deploy_status	tri deploy status
tri_deploy_logs	tri deploy logs --seed <N>
tri_deploy_remove	tri deploy remove --seed <N>

tri train / tri race

Tool	Wraps
tri_train	tri train --seed <N> --steps <N> [--hidden --lr --attn-layers --optimizer --eval-every]
tri_race_start	tri race start
tri_race_status	tri race status
tri_race_best	tri race best

trios-igla

Tool	Wraps	Exit codes
igla_search	trios-igla search [--seed --bpb-max --step-min --sha --gate-status]	0 hit, 2 no match
igla_list	trios-igla list [--last N]	0
igla_gate	trios-igla gate [--target 1.85]	0 PASS, 2 NOT YET
igla_check	trios-igla check <sha> (R9)	0 clean, 1 embargoed
igla_triplet	trios-igla triplet <index>	0

Configuration

The server resolves binary paths from the environment, falling back to PATH lookup:

Env	Default
TRIOS_TRI_BIN	tri
TRIOS_IGLA_BIN	trios-igla
RUST_LOG	info (logs go to stderr; stdout is reserved for JSON-RPC)

Claude Desktop / Cursor / Computer

~/Library/Application Support/Claude/claude_desktop_config.json (or your client's equivalent):

{
  "mcpServers": {
    "trios": {
      "command": "/absolute/path/to/trios-mcp/target/release/trios-mcp",
      "env": {
        "TRIOS_TRI_BIN":  "/abs/path/trios-trainer-igla/target/release/tri",
        "TRIOS_IGLA_BIN": "/abs/path/trios-trainer-igla/target/release/trios-igla"
      }
    }
  }
}

A copy lives at examples/claude_desktop_config.json.

Protocol

• JSON-RPC 2.0 over stdio
• Methods supported: initialize, notifications/initialized, ping, tools/list, tools/call
• Protocol version: 2024-11-05
• One JSON document per stdin line; replies are newline-delimited

tools/call returns:

{
  "isError": false,           // true iff CLI exited non-zero
  "content": [{ "type": "text", "text": "$ tri deploy status\nexit_code: 0\n\n--- stdout ---\n..." }],
  "structuredContent": {
    "bin": "tri",
    "argv": ["deploy", "status"],
    "exit_code": 0,
    "stdout": "...",
    "stderr": ""
  }
}

R-rule alignment

• R1 Rust-only.
• R5 No DONE without merged PR + green CI + ledger row. Tool results reflect the CLI verbatim; the MCP layer never invents success.
• R7 R7 triplet is owned by the wrapped binaries, forwarded unchanged.
• R9 igla_check exposes the embargo predicate. Always call it before any ledger::emit_row-equivalent action.
• NO-COMMIT-WITHOUT-ISSUE every commit references issue #1.
• CANON_DE_ZIGFICATION wraps existing binaries; touches no .t27/.tri specs or numeric/sacred-physics surfaces.

Development

cargo fmt
cargo clippy --all-targets -- -D warnings
cargo test

CI (.github/workflows/ci.yml) runs the same three checks on push and PR.

License

Apache-2.0