The MCP maintainers publish a roadmap naming five priority areas, including collapsing local servers onto Streamable HTTP over stdio and moving agent identity off pasted API keys

Sources: Model Context Protocol blog post, HN discussion
Summary: The Model Context Protocol maintainers published a roadmap naming five priority areas for the specification. Two of them are collapsing local servers onto Streamable HTTP carried over stdio rather than a separate local transport, and moving agent identity off pasted API keys and long-lived tokens onto existing standards. None of the roadmap work in the five priority areas has shipped, including Streamable HTTP over stdio, DPoP finalization, the agent identity and delegation path, the single result contract and progressive discovery. The document does name already-shipped work separately, including Tasks, subscriptions/listen and progress notifications, and the 2026-07-28 release after which a remote server is no different from any other HTTP workload.
Why it matters: Specification Enhancement Proposals inside the five named areas get expedited review and everything else queues behind them, so the document decides which proposals move rather than only describing intent.