Transports Charter changedcommunity/working-groups/transports
Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+6added
Lines−6removed
From line
24
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 24, old and new numbered
/
from line 24
2424* **Transport Bindings**: Framing, delivery, request and envelope metadata,
2525 cancellation and termination, connection lifecycle, backward compatibility, and
2626 the behavior of existing and future MCP transports. The current specification's
27 [transport overview](/specification/draft/basic/transports) defines the boundary
27 [transport overview](/specification/draft/basic/transports.md) defines the boundary
2828 between a transport binding and core protocol semantics.
2929* **Scalability and Reliability**: Transport-level connection management, resource
3030 efficiency, multiplexing, load distribution, error handling, reconnection,
from line 64
6464
6565### Related Groups
6666
67* **[SDK WG](/community/working-groups/sdk)**: Official SDKs implement transport
67* **[SDK WG](/community/working-groups/sdk.md)**: Official SDKs implement transport
6868 changes; the groups coordinate on feasibility, reference implementations, and
6969 rollout sequencing.
70* **[Tasks and Events WG](/community/working-groups/tasks-events)**: The Tasks and
70* **[Tasks and Events WG](/community/working-groups/tasks-events.md)**: The Tasks and
7171 Events WG owns Tasks and durable execution; the groups coordinate where these
7272 depend on multi-round-trip requests, request association, stateless operation, or
7373 binding behavior. Event callbacks, subscriptions, and application-level delivery
7474 semantics are owned by that group; Transports owns binding-specific carriage and
7575 guarantees.
76* **[Auth IG](/community/interest-groups/auth)** and
77 **[Security IG](/community/interest-groups/security)**: The groups coordinate on
76* **[Auth IG](/community/interest-groups/auth.md)** and
77 **[Security IG](/community/interest-groups/security.md)**: The groups coordinate on
7878 credential carriage and transport wire security while authorization mechanics and
7979 broader security requirements remain with the respective IGs.
8080
from line 117
1171173. Review and iterate on the solution to address WG feedback.
1181184. After the WG reaches consensus under its decision-making process, present the
119119 solution to Core Maintainers as an SEP through the
120 [SEP process](/community/sep-guidelines).
120 [SEP process](/community/sep-guidelines.md).
121121
122122## Resources
123123
No line in this hunk matches that.