{
  "id": "agent-host-transport:mcp-mediated",
  "_kind": "AgentHostTransport",
  "_file": "compute/agent-host-transports/mcp-mediated.yaml",
  "_cluster": "compute",
  "attributes": {
    "displayName": "MCP-mediated",
    "kind": "mcp-mediated",
    "description": "The host speaks MCP to the agent process, treating the agent itself\nas an MCP server. Useful when an agent product is designed to be\nembedded in another agent's tool surface, or when a dashboard needs\nto drive the agent through the same wire protocol it uses for tool\nservers.\n",
    "inboundMessageFormat": "Standard MCP JSON-RPC requests. Driving the agent is expressed as\n`tools/call` (or, on newer specs, `prompts/get` plus `sampling/create`)\nagainst tools the agent registers (e.g. `run_task`, `send_message`).\nThe actual JSON-RPC framing depends on the underlying MCPTransport\n(stdio / streamable-http / http-sse / websocket).\n",
    "outboundMessageFormat": "Standard MCP JSON-RPC responses and notifications. Streaming output\nis delivered via `notifications/progress` and tool-result content\nblocks; final result is the JSON-RPC `tools/call` response. From\nspec revision 2025-06-18, structured tool output and resource links\nare first-class.\n",
    "signalForwarding": "Cancel is expressed via the JSON-RPC `notifications/cancelled`\nnotification carrying the request id to cancel. Session-level\nshutdown follows the underlying MCPTransport's lifecycle (stdin EOF\non stdio; DELETE / 404 on streamable-http).\n",
    "ptySemantics": "Not applicable — MCP is a structured JSON-RPC channel; no terminal\nsemantics.\n"
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "agent-runtime-impl:claude-code.runtime@1.x",
      "to": "agent-host-transport:mcp-mediated",
      "kind": "exposes",
      "attributes": {}
    }
  ]
}