Our plans for evolving Model Context Protocol
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.
The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. This is also not an exhaustive list; we may incorporate work that isn’t mentioned here.
We value community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts.
For a technical view of our standardization process, visit the Standards Track on GitHub, which tracks how proposals progress toward inclusion in the official MCP specification.
To foster a robust developer ecosystem, we plan to invest in:
These tools will help developers confidently implement MCP while ensuring consistent behavior across the ecosystem.
For MCP to reach its full potential, we need streamlined ways to distribute and discover MCP servers.
We plan to develop an MCP Registry 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.
As MCP increasingly becomes part of agentic workflows, we’re exploring improvements such as:
Supporting the full spectrum of AI capabilities in MCP, including:
We’re implementing governance structures that prioritize:
We welcome your contributions to MCP’s future! Join our GitHub Discussions to share ideas, provide feedback, or participate in the development process.
Our plans for evolving Model Context Protocol
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.
The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. This is also not an exhaustive list; we may incorporate work that isn’t mentioned here.
We value community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts.
For a technical view of our standardization process, visit the Standards Track on GitHub, which tracks how proposals progress toward inclusion in the official MCP specification.
To foster a robust developer ecosystem, we plan to invest in:
These tools will help developers confidently implement MCP while ensuring consistent behavior across the ecosystem.
For MCP to reach its full potential, we need streamlined ways to distribute and discover MCP servers.
We plan to develop an MCP Registry 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.
As MCP increasingly becomes part of agentic workflows, we’re exploring improvements such as:
Supporting the full spectrum of AI capabilities in MCP, including:
We’re implementing governance structures that prioritize:
We welcome your contributions to MCP’s future! Join our GitHub Discussions to share ideas, provide feedback, or participate in the development process.