Skip to main content

Stateless Architecture & Discovery (Spec 2026-07-28) — Transport Layers

← All Modules
1. The Stdio Transport2. Streamable HTTP & SSE3. Stateless Architecture & Discovery (Spec 2026-07-28)

Stateless Architecture & Discovery (Spec 2026-07-28)

📚 Transport Layers⏱ 7 min⭐ 60 XP⌨ Hands-on lab

Stateless Core (Spec 2026-07-28)

The Model Context Protocol specification revision 2026-07-28 introduced fundamental architectural improvements, transitioning MCP to a true Stateless Core:

  • No Protocol Sessions: Protocol-level sessions and the Mcp-Session-Id header have been removed. MCP servers are completely stateless, making horizontal scaling, edge caching (via ttlMs / cacheScope hints), and serverless hosting seamless.
  • No Stateful Handshake: The legacy initialize and notifications/initialized lifecycle has been removed. Instead, per-request _meta fields carry protocol version and capabilities, and mandatory server/discover allows instant capability discovery (returning JSON-RPC error -32022 on unsupported protocol versions).
  • Explicit HTTP Routing Headers (SEP-2243): Every HTTP POST must declare MCP-Protocol-Version, Mcp-Method (e.g. tools/call), and—for targeted operations—Mcp-Name (e.g. query_db), allowing reverse proxies, WAFs, and gateways to route and authorize requests without parsing JSON bodies. Servers strictly validate header-to-body parity and return HTTP 400 with HeaderMismatch (-32020) on discrepancy.
  • Typed Result Discriminants (resultType): Tool responses carry a formal resultType of "complete" (final payload), "input_required" (Multi Round-Trip Request / MRTR elicitation), or "task" (asynchronous handle under io.modelcontextprotocol/tasks).
  • Subscriptions & Tasks: resources/subscribe is succeeded by subscriptions/listen, and asynchronous jobs are standardized under the official io.modelcontextprotocol/tasks extension.
💡 Key Insight: By eliminating session affinity and stateful handshakes, MCP 2026-07-28 allows any cloud load balancer or edge worker to route tool calls to any healthy replica with zero synchronization overhead.

MCP Apps & Tool Annotations

MCP Apps allow servers to return interactive UI cards rendered in sandboxed iframes. Tool annotations indicate whether an operation is read-only or destructive, enabling automatic client-side approvals for safe lookups.

LAB EXERCISEDispatch Stateless MCP Tool Invocation
+150 XP

Dispatch a tool call to an MCP endpoint passing required Mcp-Method and Mcp-Name headers under the 2026-07-28 stateless specification.

1POST a JSON-RPC tool request with Mcp-Method and Mcp-Name headers.
command-check · simulated shellhelpers: hint · solution · clear
INFINITY LAB SANDBOX v2.6 — simulated shell
Type the command for the current objective. Helpers: "hint", "solution", "clear".
$
Step 1 of 1 · type "hint" for syntax help
Knowledge Check
Press 1-4 to select1 of 3
How did the MCP 2026-07-28 specification revise connection architecture?
It mandated persistent WebSocket connections only.
It transitioned to a Stateless Core, removing protocol sessions and Mcp-Session-Id.
It added mandatory stateful session cookies.
It deprecated HTTP transport entirely.