← Back to Dashboard
1. The Stdio Transport2. Streamable HTTP & SSE3. Stateless Architecture & Discovery (Spec 2026-07-28)
Stateless Architecture & Discovery (Spec 2026-07-28)
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-Idheader have been removed. MCP servers are completely stateless, making horizontal scaling, edge caching, and serverless hosting seamless. - No Stateful Handshake: The legacy
initializeandnotifications/initializedlifecycle has been removed. Instead, per-request_metafields carry protocol version and capabilities, andserver/discoverallows instant discovery. - Explicit HTTP Routing Headers: Every HTTP POST must declare
Mcp-Method(e.g.tools/call) andMcp-Name(e.g.query_db), allowing reverse proxies, WAFs, and gateways to route requests without inspecting request bodies. - Subscriptions & Tasks:
resources/subscribeis succeeded bysubscriptions/listen, and asynchronous jobs are standardized under the officialio.modelcontextprotocol/tasksextension.
💡 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.
⌨ HANDS-ON LABDispatch Stateless MCP Tool Invocation
⭐ +150 XPDispatch 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.
OBJECTIVE 1 / 1 — type "hint" if stuck
🧪 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.