TerraYield need (blocks eo_ag#22 P0). The substrate thesis says "any MCP-speaking app is a peer," but src/ today has an MCP server (mcp_server.rs) and bespoke connectors — no MCP client that can connect to an external peer's /mcp endpoint, list its tools/resources, and invoke them. Until this exists, a TerraYield /mcp surface has no consumer: Meridian-side work builds to a contract only a design doc reads.
Acceptance
- IONe can register a peer by MCP endpoint URL, complete initialize/handshake, and enumerate tools + resources.
- Tool invocation and resource reads work over HTTP against any spec-conforming MCP server (test against a public reference server, not TerraYield).
- Peer registration is workspace-scoped and survives restart.
Anchor for #13 and the app-integration playbook; TerraYield-side sequencing in morton-analytics-llc/eo_ag#22.
TerraYield need (blocks eo_ag#22 P0). The substrate thesis says "any MCP-speaking app is a peer," but src/ today has an MCP server (mcp_server.rs) and bespoke connectors — no MCP client that can connect to an external peer's
/mcpendpoint, list its tools/resources, and invoke them. Until this exists, a TerraYield/mcpsurface has no consumer: Meridian-side work builds to a contract only a design doc reads.Acceptance
Anchor for #13 and the app-integration playbook; TerraYield-side sequencing in morton-analytics-llc/eo_ag#22.