Model Context Protocol's core maintainers published their roadmap update on August 22, 2026, setting the standard's direction for the next six to twelve months: consolidating HTTP as the sole reference transport and formalizing a governance structure that already includes a Contributor Ladder and an official feature deprecation policy.
The roadmap published in March 2026 set four workstreams: transport evolution and scalability, agent-to-agent communication, governance maturity, and enterprise readiness. According to the official Model Context Protocol blog, the following five months saw measurable progress on all four fronts, and the August update documents that progress while setting the next phase of work.
The most significant technical change is the move toward HTTP as the protocol's single transport binding, through the Transports working group. The goal is to use HTTP/2 over the current mechanism to achieve multiplexed HTTP transport without losing the security and lifecycle guarantees that subprocess execution (stdio) offers today. This work continues the migration started with the July 28, 2026 spec, which already introduced a stateless protocol core, designed so requests can be distributed across different servers behind a load balancer with no shared storage.
On the organizational side, the project formally adopted a "Contributor Ladder" (a structured progression path for contributors), and the various Working Groups now directly triage Specification Enhancement Proposals (SEPs) in their area. The spec also now has a formal feature lifecycle and deprecation policy, whose first practical applications were the features retired in the July spec.
Carlos Montiel is an enterprise AI solutions architect. He implements LLMs, Agents, RAG, and orchestrators for companies across Guatemala and Latin America. Reach out for a consultation.
Contact Carlos Montiel