MCP 2026-07-28: what the stateless revision breaks in your server or client, and when migrating is worth it
The Model Context Protocol's 2026‑07‑28 revision turns MCP from a stateful, bidirectional protocol into a stateless request/response one. The initialize handshake and the Mcp‑Session‑Id header are gone; each request now carries its protocol version, client identity and client capabilities in _meta, and state that must survive across calls has to travel as an explicit, server‑minted handle passed as a tool argument. Server‑initiated roots/list, sampling/createMessage and elicitation/create are replaced by Multi Round‑Trip Requests: the server returns a result marked input_required with the requests it needs answered, and the client retries the original call with inputResponses. Streamable HTTP now requires Mcp‑Method and Mcp‑Name headers, list and read results carry ttlMs and cacheScope, and authorization is hardened around RFC 9207 issuer validation and a formal shift away from Dynamic Client Registration toward Client ID Metadata Documents. Roots, Sampling, Logging and the legacy HTTP+SSE transport are deprecated inside a minimum twelve‑month window. The TypeScript SDK splits into v2 packages while v1.x stays frozen at 2025‑11‑25, and the Python SDK is on a 2.3.0 line. The release post names Go and C# as day‑one Tier 1 SDKs and Rust as beta, but this evidence carries no version numbers for them, and the claimed performance gains are vendor statements rather than independent measurements.
What the stateless core changes
What the revision removes
Treat this as the breakage checklist. The changelog removes, replaces or renames:
- the initialize handshake and Mcp‑Session‑Id (SEP‑2575, SEP‑2567) 2
- the HTTP GET notification endpoint, plus resources/subscribe and resources/unsubscribe, replaced by subscriptions/listen, a single long‑lived POST‑response stream that clients opt into per notification type 2
- ping, logging/setLevel and notifications/roots/list_changed; log level becomes per‑request through io.modelcontextprotocol/logLevel in _meta, and a server must not emit notifications/message for a request that did not opt in 2
- SSE stream resumability and message redelivery, including Last‑Event‑ID and SSE event IDs: a broken response stream loses the in‑flight request, and clients must re‑issue it as a new request with a new request ID 2
- the server‑initiated roots/list, sampling/createMessage and elicitation/create requests 2
- notifications/elicitation/complete and the elicitationId field added in 2025‑11‑25; servers that need to correlate an interaction across retries encode their own identifier in requestState 2
Error codes were renumbered too: resource‑not‑found moves from -32002 to -32602 (Invalid Params), HeaderMismatch from -32001 to -32020, MissingRequiredClientCapability from -32003 to -32021 and UnsupportedProtocolVersion from -32004 to -32022 2. One behavioural change is easy to miss: on modern Streamable HTTP, cancelling an in‑flight tool call closes that request's own SSE response stream rather than sending notifications/cancelled, while stdio still uses the notification 3. The Inspector renders the -32602 family as distinct Unknown Tool and Invalid Parameters panels, reading the message text to tell them apart 3.
Routing, caching and discovery additions
MRTR replaces the held‑open‑stream flows
Deprecations and the twelve‑month window
Authorization hardening and the DCR‑to‑CIMD shift
SDK boundaries: TypeScript and Python verified, others qualified
The two SDK sources here are registry metadata rather than migration guides, and they draw different lines.
- TypeScript: @modelcontextprotocol/sdk is a v1.x maintenance line at 1.32.2 that implements the spec up to 2025‑11‑25, and 2026‑07‑28 support is explicitly not planned for v1.x. Support ships in v2 as separate packages, @modelcontextprotocol/server and @modelcontextprotocol/client, and v1.x continues to receive bug fixes and security updates for at least six months after the v2 release on 2026‑07‑27 4.
- Python: the mcp package is at 2.3.0 with a reworked surface, an MCPServer class and a Client class, and the project publishes its migration guide separately 5.
The release post states that all four Tier 1 SDKs (TypeScript, Python, Go and C#) speak 2026‑07‑28 on the day of publication and that the Rust SDK supports the new spec in beta 1. No version numbers for Go, C# or Rust appear in the evidence here, and neither the TypeScript nor the Python migration guide body was captured, so step‑level instructions for removing Mcp‑Session‑Id from a specific codebase are not verified by these sources.