🗺️ The Updated MCP Roadmap

Model Context Protocol Blog | August 22, 2026 Authors: David Soria Parra & Den Delimarsky (Lead Maintainers)

Overview

We are pleased to unveil the refreshed strategic direction for the Model Context Protocol (MCP). This roadmap outlines our primary objectives for the upcoming specification cycles and beyond, ensuring the protocol evolves alongside the needs of the AI community.

"This roadmap is the result of a collaborative effort between Core Maintainers, our dedicated community of maintainers, and various Working Groups to steer the future of MCP."

📌 Quick Navigation

Priority Area	Primary Focus	Key Goal
Messaging	Agentic Primitives	Move beyond simple Request-Response
Transport	HTTP Unification	Standardize remote and local connectivity
Security	Agent Identity	Enterprise-grade, non-human authorization
Primitives	Tooling & Discovery	Standardize results and scale tool catalogs
Developer Experience	SDK Refinement	Improve ergonomics and documentation

🚀 Priority Areas

1. Agentic Messaging Primitives

The era of simple $\text{Request} \rightarrow \text{Response}$ interactions is ~~sufficient~~ no longer enough for modern agentic workflows. Current needs include longer execution loops, streamed data, and the ability to pivot tasks while they are still running.

While MCP has already introduced Tasks, subscriptions/listen, and progress updates, we need these to function as a cohesive ecosystem.

Key Objectives:

Server-Initiated Events: Implementing webhooks and channels to eliminate the need for clients to constantly poll for updates.
Cross-Group Review: A composition audit involving the Agents, Transports, and Triggers & Events Working Groups.
Specification Integration: Moving the SEP-2663 Tasks extension into the core specification.

2. HTTP-Native Transport Unification

Following the release on 2026-07-28, remote MCP servers now operate as standard HTTP workloads. This allows them to be deployed on any existing API infrastructure.

We are now expanding this model to include:

Local Integration: Supporting local servers via Streamable HTTP over stdio.
Simplification: Reducing the friction of developing both clients and servers by unifying the transport layer.

3. Agent Identity & Enterprise Security

Currently, MCP authorization relies heavily on human-in-the-loop browser approvals. However, the rise of cloud-based agents—acting autonomously or delegating to sub-agents—requires a shift in identity management.

The Security Strategy:

DPoP: Finalizing and promoting the adoption of Demonstrating Proof of Possession.
Identity Frameworks: Utilizing Workload Identity Federation, the ID-JAG grant (for Enterprise-Managed Authorization), and standard token exchanges.
Industry Alignment: Collaborating with the IETF OAuth and WIMSE working groups to ensure agent identity standards are robust.

4. Improved Primitives

Tool calling is the most utilized feature of MCP, but it faces two primary hurdles: Result Handling and Scale.

The Challenges:

Inconsistent Output: Currently, a tools/call response can provide data in multiple formats, leaving the server unsure of what the client will actually present to the LLM. We are moving toward a single, clear contract.
Context Bloat: When a server offers 100+ tools, the model's context window is flooded before the conversation even begins.

The Solution: Progressive Discovery We are implementing a system where servers provide a minimal entry point and reveal more specialized tools as the conversation's context narrows.

$\text{Context Efficiency} = \frac{\text{Relevant Tools}}{\text{Total Tool Catalog}}$

5. Improved SDK Developer Experience

The SDKs are the primary interface for developers. We are focusing on:

Ergonomics: Making the libraries more intuitive.
Conformance: Ensuring strict adherence to the specification.
AI-Ready Docs: Since many developers use agents to write MCP code, we are optimizing our documentation for LLM consumption.

🛠️ Proposal Prioritization

To manage limited maintainer resources, we are prioritizing Specification Enhancement Proposals (SEPs) that align with the areas mentioned above.

Guidelines for Contributors:

Identify which priority area your proposal fits into.
Engage with the relevant Working Group.
Refine the proposal with group members before formal submission.

🤝 Get Involved

We are actively seeking contributors for all Working Groups. Whether you are a security expert or a DX enthusiast, there is a place for you.

Ways to contribute:

Join a Working Group or Interest Group.
Visit the community channels on Discord.
Review or propose a new SEP.

For more details, please refer to the official Working and Interest Groups page.