Field notes
The MCP Stateless Migration Checklist: What Server Operators Must Ship Before July 28
The final MCP spec publishes July 28, 2026 with a stateless core. A 7-point operational checklist for server operators to be migration-ready — and audit their whole fleet.
MCPOrbit Team
MCPOrbit
- Published
- Updated
- · Updated
- Read time
- · 5 min read
The final Model Context Protocol (MCP) specification lands July 28, 2026 — the largest revision since the protocol shipped. Its headline change, a stateless core (SEP-2567), removes protocol-level sessions and the Mcp-Session-Id header from the Streamable HTTP transport. If you operate an MCP server, this is not a paint job you can defer. With two weeks on the clock, here is the exact checklist to ship a stateless-ready server — and confirm every server in your stack is covered.
Why the deadline is real
The release candidate locked on May 21 and the final spec publishes July 28. The ten-week window was for SDK maintainers and client implementers to validate against real workloads — and that window is nearly closed. Clients built against the final spec assume a stateless transport: no sticky sessions, no session header, cacheable tools/list responses. A server still leaning on session state won't cleanly break — it will quietly misbehave behind load balancers, which is worse.
Start with the audit
July 28 isn't a soft target; it's the day clients start assuming stateless. Two weeks is enough time to work this list — if you start on the fleet audit today.
About the author
MCPOrbit Team
MCPOrbit
The MCPOrbit team builds the control plane for Model Context Protocol — one view of every server in your stack and where each one sits on the migration curve.
