The Model Context Protocol finalized version 2026-07-28 on July 28, 2026, introducing a stateless core that eliminates the initialize/initialized handshake and Mcp-Session-Id header used in prior specs. Requests now carry Mcp-Method and Mcp-Name headers, allowing any request to land on any server instance—critical for load-balanced, Kubernetes-deployed, or multi-region MCP server clusters. This single architectural shift reshapes how enterprise teams deploy and scale MCP servers.
The spec also introduces a formal deprecation policy: any feature marked for removal must remain functional for a minimum 12-month window after deprecation, with documented migration paths. Three features enter deprecation: Roots (replaced by tool parameters), Sampling (switch to direct LLM-provider APIs), and Logging (migrate to stderr or OpenTelemetry). Tasks move into an Extensions framework, and authorization hardens around OAuth 2.1 / OIDC discovery. All four Tier 1 SDKs (TypeScript, Python, Go, C#) shipped support by publication day.
For practitioners, the stateless shift removes a major operational bottleneck: session-pinning, shared session stores, and reconnection logic that plagued large-scale deployments are eliminated. The 12-month deprecation floor gives teams a predictable runway to migrate away from Roots, Sampling, and Logging rather than facing surprise breaking changes. For teams building production MCP networks, the spec update signals that MCP is maturing from local-laptop integration tool toward distributable infrastructure commodity.