MCP Roadmap Targets Agent Identity and HTTP Unification

The Model Context Protocol (MCP) core maintainers and working groups have published an updated development roadmap designed to adapt the protocol for modern, long-running AI agent workloads. Moving beyond standard request-and-response patterns, the new strategy prioritizes five key areas to improve how AI models interact with external data sources and tools.

To support complex agent behaviors, the roadmap focuses on agentic messaging primitives. This includes maturing the SEP-2663 Tasks extension so it can be integrated directly into the official specification, alongside introducing server-initiated events like webhooks to eliminate the need for constant client polling. Additionally, building on the 2026-07-28 release that treated remote MCP servers as standard HTTP workloads, developers plan to unify transport modes. This unification will extend to local servers running Streamable HTTP over stdio, simplifying development across different environments.

Security is another major pillar of the updated roadmap, especially as autonomous agents increasingly run as cloud workloads without direct human supervision. The protocol will introduce standardized agent identity and delegation mechanisms, leveraging Workload Identity Federation, the ID-JAG grant for Enterprise-Managed Authorization, and Demonstrating Proof of Possession (DPoP). For developers working with tool calling, MCP aims to resolve issues with inconsistent output formats and bloated tool catalogs. A new progressive discovery feature will allow servers to expose a small initial set of tools and reveal more options as the conversation progresses.

Finally, the roadmap emphasizes improving software development kits (SDKs) to ensure they are highly intuitive, particularly since developers frequently use AI agents to write MCP code. To facilitate these updates, the community is encouraging contributions through dedicated working groups. Developers can propose experimental extensions under the SEP-2133 framework or submit Specification Enhancement Proposals to shape the protocol's future.