MCP Drops Stateful Sessions in Major 2026 Protocol Overhaul

The Model Context Protocol (MCP) released its 2026-07-28 specification this week, removing stateful session requirements from the protocol core. The shift addresses long-standing operational complexity in deploying and scaling MCP servers for agentic workflows.

From Stateful to Stateless

The previous specification required MCP servers to maintain individual client sessions, creating persistence overhead for gateways and registries. The new stateless core eliminates this requirement, allowing any request to be handled by any server instance without session tracking.

The change targets bugs and reliability issues from state management. "I cannot tell you what portion of our issues/bugs were due to the need to persist server state," said an operator of Glama, an MCP server gateway and registry. "This change will allow us to offer a lot easier way for people to use Open-Source MCP servers."

New Capabilities

Beyond the stateless transition, the specification introduces several enhancements. Multi Round-Trip Requests enable more complex interaction patterns within a single logical operation. Header-based routing provides finer control over request handling, while cacheable list results improve performance for repeated queries.

The update hardens authorization mechanisms and establishes a formal extensions framework, giving developers a structured path for protocol enhancements. A formal deprecation policy now governs how features are retired, providing clearer upgrade paths for server maintainers.

Adoption Momentum

The protocol changes arrive as MCP reaches significant adoption milestones. Tier 1 SDKs for TypeScript and Python have each surpassed 1 billion total downloads, according to the official MCP blog.

Why It Matters

MCP serves as a data and interactivity layer for agentic workflows, connecting AI models to external data sources and tools. The stateless architecture simplifies implementation of server gateways and registries, which previously needed to persist state across clients and instances.

For operators hosting open-source MCP servers, the change reduces infrastructure complexity and improves reliability. Server deployments can now scale horizontally without coordinating session state, a pattern familiar to developers of stateless HTTP APIs but previously unavailable in MCP's transport layer.

The specification update positions MCP for broader enterprise adoption, where stateless architectures align with existing cloud infrastructure patterns and operational practices.