MCP specification 2026-07-28 at a glance
The new MCP revision removes sessions and the initialize handshake so any server instance can answer any request, and moves tasks into an official extension.
What changed with MCP specification 2026-07-28
The 2026-07-28 revision drops protocol-level sessions and the Mcp-Session-Id header. Each request carries its own protocol version and client capabilities, and an optional server/discover call returns a server's versions and capabilities up front. Server-initiated requests are replaced by a Multi Round-Trip Requests pattern in which the server asks for more input and the client retries.
Requests must carry Mcp-Method and Mcp-Name headers so gateways can route them, and list results include cache hints. Tasks moved into an official extension alongside MCP Apps and enterprise-managed authorization. Roots, Sampling, Logging, the old HTTP+SSE transport, and Dynamic Client Registration are deprecated, with a minimum twelve-month deprecation window.
Why MCP specification 2026-07-28 matters for businesses
The project says the TypeScript, Python, Go, and C# SDKs supported the revision at release, with Rust in beta. Code that relies on session IDs faces the most migration work, so teams running custom MCP servers for clients should plan upgrades; the gain is simpler hosting behind ordinary load balancers.
Sources for this story
- The 2026-07-28 Specification (opens in a new tab)Official
Model Context Protocol Blog · blog.modelcontextprotocol.io
- Key Changes (2026-07-28) (opens in a new tab)Official
modelcontextprotocol.io · modelcontextprotocol.io
Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.
- #mcp
- #model-context-protocol
- #interoperability
- #standards