MCP 2026-07-28 Ships Tomorrow: What Changes at the Protocol Layer
Tomorrow's ship date is the hard migration deadline.
The MCP 2026-07-28 specification ships July 28, 2026 — one day from now. The release candidate has been locked since May 21, giving SDK maintainers a ten-week validation window. The final spec formalizes the stateless core: the initialize handshake is removed, Mcp-Session-Id is gone, and all client identity and capability data travels inline in _meta on every request. Roots, Sampling, and Logging are formally deprecated with a 12-month minimum removal window. MCP Apps and Tasks ship as first-class extensions. The Register confirmed on July 23 that Anthropic staff described it as the most substantial change to the spec since authorization was added.
Why it matters: Tomorrow's ship date is the hard migration deadline. Any MCP server that still relies on session state, Sampling, or Roots is now carrying formally deprecated dependencies. For agentic commerce infrastructure specifically, the stateless core removes the last architectural reason to avoid MCP for payment-critical server-to-server calls — a standard HTTP endpoint behind any load balancer is now a valid production MCP server.
Complete coverage including briefs and source links.