blog: MCP 2026-07-28 migration guide [DO NOT MERGE before July 28]#776
Draft
amavashev wants to merge 2 commits into
Draft
blog: MCP 2026-07-28 migration guide [DO NOT MERGE before July 28]#776amavashev wants to merge 2 commits into
amavashev wants to merge 2 commits into
Conversation
Migration guide for the MCP 2026-07-28 specification, publish date 2026-07-28 (hold merge until the spec ships). Change table by operator impact (breaking / action / new capability / deprecation) with SEP references verified row-by-row against the May 21 release candidate post; migration order by blast radius; closes on the roadmap's own enterprise gaps (audit trails, gateway behavior) and why the stateless core + routing headers make an external authority layer easier to attach. Review cycles 1-2 applied: fact-check verified every SEP row and both roadmap quotes verbatim (fixed "config portability" misquote); style pass added ellipsis to truncated quote, SEP-1865/2549 precision, runtime-authority glossary link, and softened the release-day framing to "scheduled release". Glossary linker: 3 links.
Apply 5 / modify 0 / skip 0: - add SEP-2260 to the multi-round table row (was prose-only) - "clients will cache" -> "compliant clients may cache" (table + step 5) - tag mcp -> MCP (corpus convention, 9:2) - replace pipe/water metaphor with the direct form
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This post is dated 2026-07-28 and written to publish alongside the final MCP specification release. Merging early would publish it before the spec exists.
Pre-merge checklist (July 28)
Summary
New post: MCP 2026-07-28: What Agent Operators Must Change (
blog/mcp-2026-07-28-migration-guide-agent-operators.md).Migration guide sorted by operator impact: a 12-row change table (SEP-2567 session removal, SEP-2575 handshake removal, SEP-2322/2260 multi-round restructure, SEP-2164 error-code change, SEP-2243 routing headers, SEP-2549 caching metadata, SEP-414 trace context, authorization hardening, extensions/Tasks/MCP Apps, SEP-2577 deprecations), a blast-radius-ordered migration sequence, and a closing section built on the roadmap's own statement that "audit trails, SSO-integrated auth, gateway behavior, and config portability" are deliberately left to extensions — i.e., the spec makes an external authority layer easier to attach (per-method visibility at the edge, stateless per-request decisions, standard trace propagation) while declining to provide one.
Review trail
Test plan
npm run buildpasses