Model Context Protocol project
MCP charters the Transports Working Group; its roadmap plans against a 2026-12-15 specification release
The Model Context Protocol project merged a formal charter for the Transports Working Group into its official documentation on 2026-08-26. The group, led by Kurtis Van Gent, owns transport bindings, scalability, and migration off the legacy initialization and transport-session models. Its own roadmap document, published 2026-08-25 in the working group repository, plans three priority tracks against the 2026-12-15 specification release. Neither the specification repository nor the project roadmap names a next-release date; the target appears only in the working group's document.
The Model Context Protocol project merged a formal charter for its Transports Working Group into the official documentation on 2026-08-26. The charter itself is dated 2026-08-23 and names Kurtis Van Gent as the working group lead. The group is not new: its repository has existed since January 2026 and already holds proposals, meeting notes, and decision records. What changed is formal standing. The charter page defines decision rights (spec changes need WG consensus plus Core Maintainer approval), membership rules, and a scope boundary that other groups can hold it to.
The scope is wide. Beyond transport bindings themselves - framing, delivery, connection lifecycle, backward compatibility - the charter assigns the group "transport-adjacent protocol architecture": request association, per-request metadata, stateless operation, and migration from the legacy initialization and transport-session models that the 2026-07-28 revision removed. Binding-level wire security (Origin validation, TLS, mTLS) also lands here, coordinated with the Security and Auth interest groups.
The group also published a roadmap to its repository the day before the charter merged. It plans three priority tracks "targeted for the 2026-12-15 release": tool and primitive versioning via ETag-like identifiers, HTTP over STDIO as a single transport model for local and remote servers, and pluggable transports. The date carries a caveat: the specification repository names no next-release date, and the project roadmap published 2026-08-22 committed to priority areas without one, so the working group's planning document is currently the only public surface carrying a target date for the next revision. The same document marks sessions and conversation IDs "not planned" for that release, writing down a bar any session-shaped proposal must clear after the 2026-07-28 revision removed protocol-level sessions.
The 2026-08-22 roadmap said two working groups were forming, for agent identity and core primitives. Neither has a published charter yet; the transports charter is the first group formalized since that roadmap shipped.
Related spec revisions
- MCP 2026-07-28 - current
Related publishers
How was this verified, and what are the sources?
Published · last verified · confidence 1.00.
- Spec repo PR #3300 "docs: add transports working group charter" by kurtisvg, merged 2026-08-26T03:22Z - adds docs/community/working-groups/transports.mdx (151 lines) and touches six sibling group pages plus docs.json navigation - accessed
- The charter page, live on the official docs - names Kurtis Van Gent as WG Lead, dates the initial charter 2026-08-23 in its changelog, and scopes the group to transport bindings, scalability and reliability, transport-adjacent protocol architecture including stateless operation and migration from legacy initialization and transport-session models, and binding-level wire security - accessed
- The working group's roadmap document, committed 2026-08-25T17:04Z ("docs: add upcoming transport WG tracks roadmap", PR #50) - titles itself against the 2026-12-15 specification release, lists three priority tracks (tool/primitive versioning, HTTP over STDIO, pluggable transports), four best-effort tracks, and marks sessions/conversation IDs "not planned for the 2026-12-15 release" - accessed
- The transports-wg repository - created 2026-01-08, carrying CHARTER.md, GOVERNANCE.md, proposals/, meetings/ and roadmaps/, confirming the group operated before this charter formalized it in the official docs - accessed