title: "MCP 2026-07-28 spec goes live with stateless protocol overhaul" slug: "mcp-2026-07-28-spec-goes-live-with-stateless-protocol-overhaul" published: "2026-07-31" beat: "Tools" tags: ["Tools"] creator: "Agentry Newsroom" editor: "Susanne Sperling, Editor — Human in the Loop" tools: ["Claude (Anthropic)", "Perplexity Sonar"] creativeWorkStatus: "verified" dateReviewed: "2026-07-31" aiActArticle50: "compliant" humanView: "https://agentry.news/tools/mcp-2026-07-28-spec-goes-live-with-stateless-protocol-overhaul" agentView: "https://agentry.news/agent/mcp-2026-07-28-spec-goes-live-with-stateless-protocol-overhaul"
The Model Context Protocol published its largest specification revision on July 28, 2026, removing protocol-level sessions and the Mcp-Session-Id header while SDKs across major languages ship support
Drafted by an AI agent. Verified by Susanne Sperling, Editor — Human in the Loop. AI policy.
The Model Context Protocol published its 2026-07-28 specification on July 28, 2026, delivering what AWS described as the largest and most significant revision of the protocol since its initial launch AWS Machine Learning Blog. The update makes MCP a stateless protocol by removing protocol-level sessions and eliminating the Mcp-Session-Id header from Streamable HTTP transport Model Context Protocol Changelog.
The specification had been locked as a release candidate on May 21, 2026 MCP Blog, with the final publication completing the multi-month review cycle. The revision touches transport mechanics, extension systems, and authorization frameworks—reshaping how agent applications negotiate capabilities and state management at the protocol level.
Microsoft released version 2.0 of the official MCP C# SDK implementing the 2026-07-28 revision Microsoft DevBlogs, enabling .NET developers to build stateless agent integrations immediately. The simultaneous rollout across JavaScript, Python, and C# ecosystems signals coordinated adoption across enterprise language stacks, reducing fragmentation during the protocol transition.
AWS published AgentCore Gateway support for the new specification, detailing migration paths for customers operating MCP-connected agent fleets AWS Machine Learning Blog. The timing allows cloud-native agent deployments to adopt stateless session handling without forking or maintaining dual-version support.
The removal of the Mcp-Session-Id header forces developers to handle session state at the application layer rather than relying on the protocol to track connections. This shifts responsibility upward but decouples protocol concerns from session semantics, reducing coupling between transport and business logic. Agent frameworks that previously relied on implicit session binding must now pass context explicitly through message payloads or out-of-band mechanisms.
The specification document itself is live at modelcontextprotocol.io/specification/2026-07-28, providing the normative reference for all implementations. Adoption guides and migration walkthroughs from independent developers are already circulating, signaling rapid ecosystem response to the breaking change.
For teams operating production agent systems, the statefulness removal means faster horizontal scaling and simpler load balancing—agents no longer need sticky session routing—but requires immediate audit of session-dependent code before 2026-07-28 becomes the baseline expectation across agent infrastructure.