Handshake and session removed
The protocol removes the Mcp-Session-Id header and the initialize handshake. Protocol-level sticky routing is no longer required.
Protocol readiness
Prepare for the MCP 2026-07-28 release candidate
The MCP 2026-07-28 release remains a locked release candidate, observed 2026-07-13. The final specification is scheduled for 2026-07-28; this page does not treat it as final before that date.
Protocol changes
Each request carries the connection context
The release candidate moves protocol coordination from a session handshake into self-contained requests. Applications may still manage explicit state through ordinary tool arguments.
Identity and capabilities travel with the call
Protocol version, client identity, and client capabilities move into a _meta object on every request.
Operations are visible to HTTP infrastructure
Streamable HTTP requests require Mcp-Method andMcp-Name headers alongside the request body.
Lifecycle and extensions
Deprecated does not mean removed in this release
The formal lifecycle supplies at least 12 months between deprecation and removal. Operators still need to identify dependencies and follow later changelogs.
Roots, Sampling, and Logging
These core features are deprecated under the formal lifecycle; their methods, types, and capability flags remain during the stated deprecation window.
MCP Apps and Tasks
MCP Apps and Tasks are extensions. They remain separate from the stateless protocol core and follow extension-specific lifecycles.
Authorization alignment
The candidate moves authorization closer to common OAuth and OpenID Connect deployment patterns.
Operator checklist
Inventory before changing production traffic
Work from installed servers to client releases, then keep the official changelog in the operating loop.
Inventory servers
Record every installed server, transport, owner, and deployed SDK version before planning a migration.
Find session dependencies
Identify code, gateways, and tests that depend on Mcp-Session-Id, initialize, or sticky routing.
Review deprecated features
Check Roots, Sampling, and Logging usage against the formal lifecycle and document any replacement work.
Track client releases
Verify installed client versions and follow official changelogs through the final specification publication.
Client readiness
No catalog client is marked ready without owner evidence
Checked 2026-07-13. This table starts fail-closed and changes only when a reviewed, client-owner source supports a more specific statement.
| Client | Readiness | Evidence note |
|---|---|---|
| ChatGPT web | Unknown | no official statement located as of 2026-07-13 |
| ChatGPT desktop | Unknown | no official statement located as of 2026-07-13 |
| Claude Code | Unknown | no official statement located as of 2026-07-13 |
| Cursor | Unknown | no official statement located as of 2026-07-13 |
| Codex | Unknown | no official statement located as of 2026-07-13 |
| Gemini CLI | Unknown | no official statement located as of 2026-07-13 |
| VS Code | Unknown | no official statement located as of 2026-07-13 |
ResolveMesh surfaces
Keep protocol readiness separate from pair compatibility
The public catalog records reviewed client and tool requirements. It does not turn release-candidate support into a compatibility claim.
Compare all pairs
Review the seven-client by five-tool evidence matrix.
Open compatibilityInspect canonical examples
Read the dated receipts for Codex with GitHub MCP and Claude Code with GitHub MCP.
Open the Codex pair Open the Claude Code pairRequest a founder-reviewed watch
A request records interest only; it creates no account, monitoring promise, or charge.
Open the watch-request funnelPrimary sources
References
Both protocol-maintainer posts were checked 2026-07-13. This guide paraphrases only the bounded fact set recorded in the approved implementation contract.
MCP 2026-07-28 specification release candidate
Protocol-maintainer overview of the locked release candidate, stateless core, extensions, authorization changes, deprecations, and finalization timeline; observed 2026-07-13.
Read the primary sourceMCP 2026-07-28 beta SDKs
Protocol-maintainer SDK readiness post for the release-candidate validation window; observed 2026-07-13.
Read the primary source