Skip to content
Tech News
← Back to articles

The New MCP Roadmap

read original more articles
Why This Matters

The updated MCP roadmap signifies a major step forward in enhancing protocol capabilities to support modern, agentic workloads and streamline deployment across various infrastructures. These developments will improve real-time communication, flexibility, and scalability for developers and organizations adopting MCP. As a result, the protocol will better serve the evolving needs of the tech industry and consumers relying on more dynamic and efficient data exchanges.

Key Takeaways

Today we’re excited to publish an updated roadmap for the Model Context Protocol (MCP), covering the next specification release and beyond.

The roadmap sets the direction for protocol work over the coming months. It was developed by the Core Maintainers together with our community of maintainers and Working Groups.

Priority areas#

The roadmap is organized into five priority areas. Several of them pick up work that the previous roadmap listed as on the horizon, including server-initiated events, result type improvements, and agent identity, which have since matured enough to become priorities in their own right. Each area is owned by a set of Core Maintainers and one or more Working Groups.

Agentic messaging primitives#

Modern agentic workloads no longer fit the standard request-and-response pattern. Loops can run for longer, servers can push streamed results, and there is a clear need to steer work mid-flight. MCP has been growing to meet these requirements, introducing Tasks, subscriptions/listen , and progress notifications. We want to make sure that we not only offer the right primitives for the job, but also that they work well together. The work here spans server-initiated events (webhooks and channels, so clients aren’t left polling for results), a composition review across the Agents, Transports, and Triggers & Events Working Groups, and maturing the Tasks extension (SEP-2663) so it can move into the specification.

HTTP-native transport unification and hardening#

With the 2026-07-28 release, a remote MCP server is now no different from any other HTTP workload, making it easy to host and operate one on any infrastructure that developers and organizations already use for their APIs and services. The model has proven to scale, and we want to stretch it to cover other deployment modes as well, including local servers speaking Streamable HTTP over stdio. Unifying on one transport lets us simplify MCP server and client development even further.

Agent identity and enterprise-ready security#

... continue reading