Our plans for evolving Model Context Protocol (H1 2025)The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and future direction for the first half of 2025, though these may change significantly as the project develops.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 encourage community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts.Our top priority is enabling remote MCP connections, allowing clients to securely connect to MCP servers over the internet. Key initiatives include:Service Discovery: Defining how clients can discover and connect to remote MCP servers. Stateless Operations: Thinking about whether MCP could encompass serverless environments too, where they will need to be mostly stateless. To help developers build with MCP, we want to offer documentation for:Client Examples: Comprehensive reference client implementation(s), demonstrating all protocol features
Protocol Drafting: Streamlined process for proposing and incorporating new protocol features
Looking ahead, we’re exploring ways to make MCP servers more accessible. Some areas we may investigate include:Package Management: Standardized packaging format for MCP servers
Installation Tools: Simplified server installation across MCP clients
Sandboxing: Improved security through server isolation
Server Registry: A common directory for discovering available MCP servers
Interactive Workflows: Better handling of user permissions and information requests across agent hierarchies, and ways to send output to users instead of models. Community-Led Standards Development: Fostering a collaborative ecosystem where all AI providers can help shape MCP as an open standard through equal participation and shared governance, ensuring it meets the needs of diverse AI applications and use cases.
[Standardization] Considering standardization through a standardization body.
We welcome community participation in shaping MCP’s future. Visit our GitHub Discussions to join the conversation and contribute your ideas. Modified at 2025-03-12 07:37:20