MCP Version 5: Stateless Core, Extended Authorization, and Formal Extensions

The Model Context Protocol (MCP) released version 2026-07-28, its fifth major iteration. The core change is a shift from a stateful bidirectional protocol to a stateless request/response model, enabling MCP servers to run as standard HTTP workloads on serverless and edge infrastructure without session management. Authorization is strengthened with production-grade OAuth 2.0/OIDC support, directly integrating with Entra, Okta, and similar systems. The extension framework is formalized, incorporating MCP Apps (interactive UI in conversations) and Tasks (long-running operations). New headers Mcp-Method and Mcp-Name allow gateway-level routing without JSON parsing. Multi-round trip requests (MRTR) handle mid-task user confirmations. Deprecated features (Roots, Sampling, Logging, HTTP+SSE transport) get a guaranteed 12-month transition window. SDKs for TypeScript, Python, Go, C# are updated; Rust SDK is in beta. Monthly downloads approach 500 million. AWS, Microsoft, Cloudflare, Google Cloud, Figma, Supabase, and Honeycomb have announced support. Breaking changes require migration; early testers report simplified processes.
Key insights
Stateless Core Removes Major Operational Barriers
The move to a stateless request/response model eliminates the need for sticky sessions and session IDs, allowing MCP servers to be deployed like ordinary HTTP services. This enables horizontal scaling, load balancing, serverless deployment, and edge computing, drastically lowering the infrastructure complexity for building and running MCP servers.
Authorization Upgrades Align MCP with Enterprise Identity Standards
The new spec mandates issuer validation to close authorization server confusion vulnerabilities, deprecates Dynamic Client Registration in favor of Client Instance Metadata Documents, and supports direct integration with enterprise identity providers like Entra and Okta. This makes MCP suitable for production environments with strict security requirements.
Formal Extension Framework Signals Protocol Maturity
By standardizing MCP Apps and Tasks as versioned extensions, the protocol moves beyond basic tool calling to support interactive UI rendering within conversations and long-running asynchronous operations. This formalization indicates the protocol is evolving to cover a broader range of AI-agent interaction patterns.
Deprecation Policy with 12-Month Window Provides Production Stability
For the first time, MCP introduces a formal deprecation policy guaranteeing at least 12 months of support for deprecated features. This gives teams running production MCP servers a predictable timeline to plan upgrades, reducing the risk of sudden breaking changes.
Strong Ecosystem Backing from Major Cloud Providers and Tool Vendors
AWS (Bedrock AgentCore), Microsoft (Foundry), Cloudflare (Workers), Google Cloud, Figma, Supabase, and Honeycomb have all announced support for the new specification. Combined with nearly 500 million monthly downloads and over 1 billion cumulative SDK downloads, this signals broad industry adoption.
Migration Requires Effort but SDKs and Guides Are Available
The new spec includes breaking changes, particularly for implementations relying on session identifiers. SDK teams have simplified migration based on early feedback, but the cost varies by project. Production users are advised to review the full changelog and migration guide before upgrading.