MCP 2026-07-28 goes final: sessions die, HTTP wins
The largest MCP revision since launch ships a stateless core — no session handshake, ordinary HTTP scaling, and a deprecation clock for anything still assuming sticky sessions.
Source: Model Context Protocol
July 28, 2026 is the date that matters for anyone hosting a remote MCP server. Spec revision 2026-07-28 — the biggest change since launch — makes the protocol stateless at the core: self-contained requests, no initialize handshake as the default path, and no reliance on session affinity to keep agents talking.
What that unlocks:
- Load-balance MCP like any other HTTPS API
- Run discovery and tool calls on commodity HTTP infra
- Align auth more closely with OAuth / OIDC deployments
What might break: sticky-session setups, clients that still assume a long-lived Mcp-Session-Id, and experimental patterns that lived outside the new extensions model. Deprecated pieces keep working for a while — but “a while” is not a migration plan.
Why it matters: ChatGPT, Claude connectors, and hosted agents already prefer public HTTPS. A stateless spec is how MCP stops feeling like a desktop plugin protocol and starts feeling like platform plumbing.
If you ship a remote server, validate against the new SDKs before your next release train. Browse production-ready remotes in the directory, or connect Influzer’s own discovery endpoint via the setup guide.