Originally published on rohitraj.tech
The MCP 2026-07-28 specification goes final on July 28, 2026, and it rewrites the protocol to be stateless: no more initialize handshake (SEP-2575), no Mcp-Session-Id header (SEP-2567), with protocol version and client info moving into a _meta field on every request. That one change lets MCP servers deploy like any stateless service — serverless and Kubernetes autoscaling finally work without sticky sessions — but it breaks every server that assumed a session. Here is the full before/after migration in TypeScript: the stateless transport config, per-request _meta, the new Tasks extension lifecycle, the -32602 error change, the six auth-hardening SEPs, and exactly which servers should wait.
Read the full version with code samples, diagrams, and architecture details: MCP Goes Stateless: Migrate Your Server Before the 2026-07-28 Spec
More engineering notes: rohitraj.tech/en/notes
Top comments (0)