Where MCP Is Headed Next
The MCP maintainers published an updated roadmap.
Since March, MCP went stateless (no more session handshakes), turned Tasks into an official extension for long-running work, and shipped enterprise auth pieces like issuer validation and Client ID Metadata Documents.
Next up: one HTTP-native transport instead of separate stdio and HTTP paths, real agent identity (workload federation, token exchange), and progressive tool discovery for large catalogs. No firm dates yet.
MCP is leaving its single-session, request/response origins behind for something built for long-running, multi-agent systems.