Update roadmap to reflect November 2025 release priorities #1570
+22
−18
Conversation
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
Align roadmap with the five key priorities outlined in the September 26th blog post: - Asynchronous operations for long-running tasks - Statelessness and scalability improvements - Server identity via .well-known URLs - Official extensions for industry-specific patterns - SDK support standardization and tiering Retained validation and multimodality sections as longer-term goals. Removed completed Registry work and deprioritized authentication items. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
bhosmer-ant
approved these changes
Sep 29, 2025
| <Info>Last updated: **2025-09-26**</Info> | ||
|
|
||
| The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and direction for approximately **the next six months**, though these may change significantly as the project develops. To see what's changed recently, check out the **[specification changelog](/specification/2025-06-18/changelog/)**. | ||
| The Model Context Protocol is rapidly evolving. This page outlines our priorities for **the next release on November 25th, 2025**, with a release candidate available on November 11th, 2025. To see what's changed recently, check out the **[specification changelog](/specification/2025-06-18/changelog/)**. |
There was a problem hiding this comment.
Suggested change
| The Model Context Protocol is rapidly evolving. This page outlines our priorities for **the next release on November 25th, 2025**, with a release candidate available on November 11th, 2025. To see what's changed recently, check out the **[specification changelog](/specification/2025-06-18/changelog/)**. | |
| The Model Context Protocol is rapidly evolving. This page outlines our priorities for **the next release on November 25th, 2025**, with a release candidate available on November 11th, 2025. To see what's changed recently, check out the **[specification changelog for the current release](/specification/2025-06-18/changelog/)**. |
pja-ant
reviewed
Sep 30, 2025
|
|
||
| We plan to develop an [**MCP Registry**](https://github.com/orgs/modelcontextprotocol/discussions/159) that will enable centralized server discovery and metadata. This registry will primarily function as an API layer that third-party marketplaces and discovery services can build upon. | ||
|
|
||
| ## Multimodality |
There was a problem hiding this comment.
Is this still on the roadmap?
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.
Align roadmap with the five key priorities outlined in the September 26th blog post:
Retained validation and multimodality sections as longer-term goals. Removed completed Registry work