docs: MCP Roadmap fully rewritten - new strategic priorities, named Core Maintainers, DPoP and HTTP/2-over-stdio direction - #1203
Merged
Conversation
…ore Maintainers, DPoP and HTTP/2-over-stdio direction Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
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
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.
Night shift report
WHY THIS MATTERS: The MCP roadmap (modelcontextprotocol.io/development/roadmap) was fully rewritten today (2026-08-22) — not a minor edit. The old four-area structure (Transport Evolution, Agent Communication, Governance, Enterprise) is gone. In its place is a five-area plan with named Core Maintainers per area, specific SEPs called out as deliverables, and a clear "this roadmap period" / "beyond this" split. Anyone building MCP servers or tracking the protocol's direction needs to know the priorities have materially shifted.
HIGHLIGHTS:
tools/callinterface redesign planned to resolve thecontent+structuredContentambiguity that's already producing diverging implementations.Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning