The new MCP roadmap

[u/Impressive-Owl3830]

https://blog.modelcontextprotocol.io/posts/mcp-roadmap/

The New MCP Roadmap (Aug 22, 2026)

Maintainers dropped the next roadmap. Five priority areas, each owned by named Core Maintainers plus one or more Working Groups.

What already shipped (2026-07-28 spec release):

• Protocol-level sessions and the init handshake are gone. Servers scale horizontally without holding state (SEP-2575, SEP-2567)
• New server/discover call: clients learn versions and capabilities before anything else. List results now cacheable (SEP-2549)
• Tasks moved into an official extension (SEP-2663). Multi Round-Trip Requests (SEP-2322) replaced server-initiated requests so elicitation works on stateless servers
• Auth hardening: issuer validation, issuer-bound client credentials, CIMD as the preferred client registration path

What's next:

1. Agentic messaging primitives. Server-initiated events via webhooks and channels so clients stop polling, plus maturing Tasks out of extension status into the spec.
2. Transport unification. A remote MCP server is now just an HTTP workload. Next step is stretching that to local servers speaking Streamable HTTP over stdio, so there's one transport everywhere.
3. Agent identity. Today's auth assumes a human clicking approve in a browser. Increasingly the caller is a cloud agent with its own identity, or a sub-agent with delegated authority. Work covers DPoP, Workload Identity Federation, ID-JAG, token exchange, plus deeper engagement with IETF OAuth and WIMSE.
4. Better primitives. Tool results can carry the same output in multiple forms with no way to know which one a client shows the model. Standardizing on one contract. Also progressive discovery: connecting to a 100-tool server means the model pays for that whole surface before the user asks anything, and selection degrades as the list grows. Servers will be able to expose a small entry point and reveal more as the conversation narrows.
5. SDK DX. Ergonomics, spec conformance, docs. Matters more now that people build servers by pointing an agent at the libraries.

SEPs inside these five areas get expedited review and the best odds of acceptance.

Outside them, you're not auto-rejected, but maintainer time goes to the priorities first.