docs: MCP_MESH_CONFIG — operator reference for 6-server Trinity mesh#118
Open
gHashTag wants to merge 1 commit into
Open
docs: MCP_MESH_CONFIG — operator reference for 6-server Trinity mesh#118gHashTag wants to merge 1 commit into
gHashTag wants to merge 1 commit into
Conversation
Captures the canonical MCP server layout across the Trinity repos so any client (Claude Desktop / Cursor / Computer) can be wired to all six servers with a single config copy-paste: 1. trios — Rust server on port 9005 + Tailscale remote 2. trios-railway — production MCP endpoint 3. trios-mcp — stdio wrapper over tri + trios-igla 4. t27 — traceability + GitButler 5. opencode — github + filesystem + trinity-sync 6. combined — Claude Desktop/Cursor/Computer one-shot config Plus a pre-flight checklist per server and a pointer to the NASA-style verification report skill for formal MCP-mesh acceptance. Source: operator-supplied 2026-05-03 14:30 +07. R5: this is documentation, not code. Operator paths are placeholders (/Users/playra/...) — replace before applying. Anchor: phi^2 + phi^-2 = 3. Refs: - trios#446 EPIC - trios-railway#116 O(1) MCP v3 design
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
Single page documenting the canonical MCP server mesh across the Trinity stack so any client (Claude Desktop / Cursor / Computer) can be wired with a one-shot JSON copy-paste. Operator-supplied 2026-05-03 14:30 +07.
6-server layout
trioscargo run -p trios-servertrios-railwaytrios-iglatri+trios-iglabinst27-traceability+gitbutlerENFORCE_L1=trueopencodeclaude_desktop_config.jsonpathPlus the pre-flight checklist (6
probesteps per server) and pointer to thenasa-mission-reportskill for formal R5-honest MCP-mesh acceptance ("отчёт NASA по MCP-mesh" → P-01 health / P-02 auth / P-03 tools / P-04 canon-regex / P-05 latency / P-06 offline-fallback).Why in
trios-railwayThis repo owns the production MCP endpoint (
trios-railway-production-d4d6.up.railway.app/mcp). The mesh doc lives alongside it so operator reaches both with onegit pull.R5 honesty
Documentation only, no code changes. Operator paths (
/Users/playra/...) are placeholders to be replaced per machine. The NASA probe sheet is a pointer to a future verification run, not a claim that the mesh is already verified end-to-end.References
🌻
phi^2 + phi^-2 = 3 · TRINITY · MESH LOCKED