thevibeworks · claude-yolo · Aug 26, 2026 · Aug 26, 2026
diff --git a/content/.metadata.json b/content/.metadata.json
diff --git a/content/mcp/community/interest-groups/auth.md b/content/mcp/community/interest-groups/auth.md
@@ -41,7 +41,7 @@ The Authorization Interest Group is the single chartered venue for MCP authoriza
 ### Related Groups
 
 * **[Security IG](/community/interest-groups/security)**: token-audience confusion, issuer validation, and account-linking risks sit at the boundary between the two groups
-* **Transports WG**: authorization is currently specified at the HTTP transport level; changes to transports affect where credentials are carried
+* **[Transports WG](/community/working-groups/transports)**: authorization is currently specified at the HTTP transport level; changes to transports affect where credentials are carried
 * **Agents WG**: delegated/on-behalf-of access and consent for multi-agent chains overlap heavily with agentic use cases
 * **[Server Card WG](/community/working-groups/server-card) / [Registry](/community/working-groups/registry)**: client and server identity, discovery metadata, and trust establishment intersect with how authorization servers and resource servers are located and verified
 * **SDK Maintainers**: SDKs ship the auth client implementations; IG findings should inform cross-SDK auth ergonomics and defaults

diff --git a/content/mcp/community/interest-groups/security.md b/content/mcp/community/interest-groups/security.md
@@ -71,7 +71,7 @@ scopes validated problems into focused Working Groups or [SEPs](/community/sep-g
 * **[Server Card WG](/community/working-groups/server-card) / [Registry WG](/community/working-groups/registry)**:
   server identity, provenance, and discovery metadata intersect with admission and supply-chain
   concerns
-* **Transports WG**: stdio process isolation and unauthenticated method surface
+* **[Transports WG](/community/working-groups/transports)**: stdio process isolation and unauthenticated method surface
 * **SDK Maintainers**: coordinated handling of SDK security advisories and cross-SDK security
   defaults
 

diff --git a/content/mcp/community/working-groups/agents.md b/content/mcp/community/working-groups/agents.md
@@ -62,7 +62,7 @@ primitives. The WG evaluates those questions through its design work.
 
 ### Related Groups
 
-* **[Transports WG](https://github.com/modelcontextprotocol/transports-wg)** -
+* **[Transports WG](/community/working-groups/transports)** -
   Task polling, multi-round-trip requests, stateless operation, and request
   association depend on transport and message-flow semantics.
 * **[Triggers and Events WG](/community/working-groups/triggers-events)** -

diff --git a/content/mcp/community/working-groups/interceptors.md b/content/mcp/community/working-groups/interceptors.md
@@ -31,7 +31,7 @@ The Interceptors Working Group exists to standardize how context operations are
 
 ### Related Groups
 
-* **Transports WG** — interceptors operate on MCP message flows whose delivery behavior depends on the transport; coordination needed on transport-level interception points.
+* **[Transports WG](/community/working-groups/transports)** — interceptors operate on MCP message flows whose delivery behavior depends on the transport; coordination needed on transport-level interception points.
 * **Gateways IG** — gateways are a key deployment model for interceptors; coordination needed on gateway-based interceptor patterns and shared concerns around routing, policy, and observability.
 
 ## Leadership

diff --git a/content/mcp/community/working-groups/sdk.md b/content/mcp/community/working-groups/sdk.md
@@ -34,7 +34,7 @@ The SDK Working Group exists to keep the official MCP SDKs consistent, conforman
 
 ### Related Groups
 
-* **Transports WG**: Transport implementations are a substantial part of every SDK. The SDK WG coordinates with the Transports WG on rollout sequencing when transport SEPs land.
+* **[Transports WG](/community/working-groups/transports)**: Transport implementations are a substantial part of every SDK. The SDK WG coordinates with the Transports WG on rollout sequencing when transport SEPs land.
 * **Conformance Testing**: Tier assignments depend on conformance scores. The SDK WG consumes conformance results and feeds back gaps in test coverage.
 * **All specification-producing WGs**: The SDK WG is a downstream consumer of accepted SEPs and coordinates reference-implementation timing with the originating group.
 

diff --git a/content/mcp/community/working-groups/transports.md b/content/mcp/community/working-groups/transports.md
@@ -0,0 +1,154 @@
+> ## Documentation Index
+> Fetch the complete documentation index at: https://modelcontextprotocol.io/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Transports Charter
+
+> Charter for the MCP Transports Working Group.
+
+## Group Type
+
+**Working Group**
+
+## Mission Statement
+
+The Transports Working Group evolves MCP transport bindings and transport-adjacent
+protocol architecture so implementations remain interoperable, scalable, reliable,
+and easy to operate across local and remote deployments. The WG produces transport
+proposals, SEPs, implementation evidence, and guidance. The
+[working group repository](https://github.com/modelcontextprotocol/transports-wg) and
+its [upstream charter](https://github.com/modelcontextprotocol/transports-wg/blob/main/CHARTER.md)
+maintain the WG's current technical focus, proposal strategy, and supporting detail
+within these boundaries.
+
+## Scope
+
+### In Scope
+
+* **Transport Bindings**: Framing, delivery, request and envelope metadata,
+  cancellation and termination, connection lifecycle, backward compatibility, and
+  the behavior of existing and future MCP transports. The current specification's
+  [transport overview](/specification/draft/basic/transports) defines the boundary
+  between a transport binding and core protocol semantics.
+* **Scalability and Reliability**: Transport-level connection management, resource
+  efficiency, multiplexing, load distribution, error handling, reconnection,
+  resumption, and the delivery and ordering guarantees offered by a binding.
+* **Transport-Adjacent Protocol Architecture**: Protocol-wide message-flow concerns
+  required for scalable, interoperable bindings, including request association,
+  per-request metadata, stateless operation, and migration from legacy initialization
+  and transport-session models.
+* **Transport Security**: Binding and envelope security requirements such as Origin
+  validation, TLS, mTLS, and certificate handling, coordinated with the Security IG.
+  Credential carriage is coordinated with the Auth IG.
+* **Validation and Guidance**: Reference implementations, experiments, implementation
+  evidence, and documentation needed to evaluate proposals and help implementers
+  adopt agreed transport behavior. Supporting material is maintained in the upstream
+  [documentation](https://github.com/modelcontextprotocol/transports-wg/tree/main/docs).
+  The WG contributes transport scenarios and requirements to the Conformance Testing
+  project, whose maintainers own the conformance suite.
+* **Cross-Cutting Coordination**: Transport implications of work owned by other MCP
+  groups, without taking ownership of their application-layer features.
+
+The upstream [scope statement](https://github.com/modelcontextprotocol/transports-wg/blob/main/CHARTER.md#scope)
+provides supporting context but cannot expand the boundaries in this charter.
+
+### Out of Scope
+
+* Application-layer behavior for MCP primitives such as tools, resources, prompts,
+  tasks, agents, or events, including application state, application-session meaning,
+  task lifecycle, and event or subscription semantics. The WG coordinates where those
+  features depend on binding or message-flow behavior.
+* Domain-specific extensions and implementation-specific product or business concerns.
+* SDK APIs and implementation details unrelated to transports.
+* Authorization protocol mechanics, credential and token semantics, application
+  identity, and authorization policy. The WG coordinates with the relevant groups on
+  how bindings carry agreed authorization data.
+* Ownership of the MCP conformance suite. The WG contributes transport requirements
+  and scenarios in coordination with its maintainers.
+
+### Related Groups
+
+* **[SDK WG](/community/working-groups/sdk)**: Official SDKs implement transport
+  changes; the groups coordinate on feasibility, reference implementations, and
+  rollout sequencing.
+* **[Agents WG](/community/working-groups/agents)**: The Agents WG owns Tasks and
+  durable execution; the groups coordinate where these depend on multi-round-trip
+  requests, request association, stateless operation, or binding behavior.
+* **[Triggers and Events WG](/community/working-groups/triggers-events)**: Event
+  callbacks, subscriptions, and application-level delivery semantics are owned by that
+  group; Transports owns binding-specific carriage and guarantees.
+* **[Auth IG](/community/interest-groups/auth)** and
+  **[Security IG](/community/interest-groups/security)**: The groups coordinate on
+  credential carriage and transport wire security while authorization mechanics and
+  broader security requirements remain with the respective IGs.
+
+## Leadership
+
+The current WG Lead is
+[Kurtis Van Gent](https://github.com/kurtisvg).
+
+## Authority & Decision Rights
+
+| Decision Type                       | Authority Level                                        |
+| ----------------------------------- | ------------------------------------------------------ |
+| Meeting logistics & scheduling      | WG Leads (autonomous)                                  |
+| Proposal prioritization within WG   | WG Leads (autonomous)                                  |
+| SEP triage & closure (in scope)     | WG Leads (autonomous, with documented rationale)       |
+| Technical design within scope       | WG consensus                                           |
+| Spec changes (additive)             | WG consensus → Core Maintainer approval                |
+| Spec changes (breaking/fundamental) | WG consensus → Core Maintainer approval + wider review |
+| Scope expansion                     | Core Maintainer approval required                      |
+| WG Member approval                  | WG Member sponsors                                     |
+
+## Membership
+
+Current WG Members are listed in the upstream
+[group membership roster](https://github.com/modelcontextprotocol/transports-wg/blob/main/GOVERNANCE.md#members).
+
+## Operations
+
+The WG holds a regular weekly meeting, with the current time and joining details listed
+at [meet.modelcontextprotocol.io](https://meet.modelcontextprotocol.io). Topics are
+discussed asynchronously in `#transports-wg` on the
+[MCP Discord](https://discord.gg/6CSzBmMkjX).
+
+Work follows a problem-first workflow:
+
+1. Create a core problem statement in the
+   [working group repository](https://github.com/modelcontextprotocol/transports-wg) to
+   align the WG on the problem and its requirements.
+2. Work with other interested participants to define a solution.
+3. Review and iterate on the solution to address WG feedback.
+4. After the WG reaches consensus under its decision-making process, present the
+   solution to Core Maintainers as an SEP through the
+   [SEP process](/community/sep-guidelines).
+
+## Resources
+
+* [modelcontextprotocol/transports-wg](https://github.com/modelcontextprotocol/transports-wg)
+  * [Proposals](https://github.com/modelcontextprotocol/transports-wg/tree/main/proposals)
+  * [Supporting documentation and decision records](https://github.com/modelcontextprotocol/transports-wg/tree/main/docs)
+  * [Meeting notes](https://github.com/modelcontextprotocol/transports-wg/tree/main/meetings)
+
+## Deliverables & Success Metrics
+
+### Active Work Items
+
+See [open pull requests](https://github.com/modelcontextprotocol/transports-wg/pulls)
+and the [`roadmaps/` directory](https://github.com/modelcontextprotocol/transports-wg/tree/main/roadmaps).
+
+### Success Criteria
+
+* Adopted transport-agnostic protocol behavior remains consistent across transports,
+  while binding-specific differences are explicit and validated by implementation
+  evidence and applicable conformance scenarios.
+* Transport changes that affect official SDKs are coordinated with the SDK WG and have
+  clear implementation guidance.
+* Decisions, proposal status, and supporting rationale remain publicly discoverable in
+  or linked from the working group repository.
+
+## Changelog
+
+| Date       | Change          |
+| ---------- | --------------- |
+| 2026-08-23 | Initial charter |
diff --git a/content/mcp/community/working-groups/triggers-events.md b/content/mcp/community/working-groups/triggers-events.md
@@ -31,7 +31,7 @@ The Triggers and Events Working Group exists to define how MCP servers proactive
 
 ### Related Groups
 
-* **Transports WG** — delivery and ordering guarantees depend on transport capabilities; callback semantics must be coherent across stdio, Streamable HTTP, and future transports.
+* **[Transports WG](/community/working-groups/transports)** — delivery and ordering guarantees depend on transport capabilities; callback semantics must be coherent across stdio, Streamable HTTP, and future transports.
 * **Agents WG** — [SEP-1686 (Tasks)](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1686) identifies webhook-style task completion notifications as a future consideration; this WG owns that mechanism.
 
 ## Leadership

diff --git a/content/support/10310342-how-do-i-log-out-of-all-active-sessions.md b/content/support/10310342-how-do-i-log-out-of-all-active-sessions.md
@@ -38,7 +38,7 @@ To regain access to your account on any device, you'll need to authenticate agai
 
 If you used your Claude account to authenticate into Claude Code, you can manage your authorization tokens by navigating to **[Settings > Claude Code](https://claude.ai/settings/claude-code)**. To remove a token and log out of Claude Code, click the trash can icon.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1608263923/b4fa7d6f6f08f2adffb4ea63bc58/image+%287%29.png?expires=1787712300&amp;signature=b18b48ecf2c56f11469652262211fd9a124b43d4085b08bb87d4cb64dcadcc58&amp;req=dSYnHst4nohdWvMW1HO4zVuHihv612W4AQofdwM8qVflry0MOXfs7knSUZTK%0AlIP62WRaqqAuibusQss%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1608263923/b4fa7d6f6f08f2adffb4ea63bc58/image+%287%29.png?expires=1787727600&amp;signature=eff1a4f2870aadcce24f0755784001c895bb884bac0aa12f3b81105dae01c0ec&amp;req=dSYnHst4nohdWvMW1HO4zVuHihv61GC9AQofdwM8qVcCoeMM%2BBDii84R9IK9%0AsQd0pl%2BLHgCCpytafGE%3D%0A)
 
 ## Unable to access your account?
 

diff --git a/content/support/10366376-how-can-i-delete-my-claude-console-account.md b/content/support/10366376-how-can-i-delete-my-claude-console-account.md
@@ -36,14 +36,14 @@ If you followed the steps above to delete your Console organization but want to
 
 If you have an outstanding balance, you will see a message during the deletion flow that prompts you to pay the balance first by routing you to [Settings > Billing](https://platform.claude.com/settings/billing).
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1973957766/5c2dd87c0818a0400099a833c9b3/4cc3130a-f696-4967-9fe3-e5623c6f02bd?expires=1787712300&amp;signature=a13870346821fdf915245b4b9e7eabaea01449ce6067750a94fef3232dac51c6&amp;req=dSkgFcB7moZZX%2FMW1HO4zbYXUBBlXeYYFZRyvJPpBZ8xEU6RaFyIrl6JBpP2%0AkQ4VK%2BnUU3bib%2BhvGOQ%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1973957766/5c2dd87c0818a0400099a833c9b3/4cc3130a-f696-4967-9fe3-e5623c6f02bd?expires=1787727600&amp;signature=5ea5bf654d41807505dc58a5e395ccd82015ce1382bf0ac5331b58d461e768fa&amp;req=dSkgFcB7moZZX%2FMW1HO4zbYXUBBlXuMdFZRyvJPpBZ8YSbpoQ4Nh%2Frm2Z8g3%0AN12nQz9ynF0omMbAVPE%3D%0A)
 
 You must pay this outstanding balance before you’re able to move forward with the deletion process.
 
 ### I’m seeing a message about contacting the Support team when I try to delete my Console organization.
 
 There are some scenarios where you will need to contact our team to delete your account. If this is the case, it will be noted when you try to delete your organization:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1973957765/19dda72a40db95d78c00c27a1a1c/6ce89be6-93ce-409c-bbea-d34be09db348?expires=1787712300&amp;signature=d6e77d3d4b31384060e4bdf9fca8327c817ba4d2e923eed4eb13fa3b6f6cffe1&amp;req=dSkgFcB7moZZXPMW1HO4zRW12%2BLKeab6ZxDZGlqR6GhXcIsc4jbJhp2cDwT%2F%0ApyD79fenWVMD96wylOA%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1973957765/19dda72a40db95d78c00c27a1a1c/6ce89be6-93ce-409c-bbea-d34be09db348?expires=1787727600&amp;signature=9628ae0479624e9d3ff592ac5fa18bbe732c5844f06f6dd366da65a78281b478&amp;req=dSkgFcB7moZZXPMW1HO4zRW12%2BLKeqP%2FZxDZGlqR6GhEl3hF0m3HMGC%2Bh8%2FL%0AvX7510%2BmX2apiB2vrxc%3D%0A)
 
 If you are seeing this message, this indicates that your Console organization cannot be deleted via the self-service pathway.
diff --git a/.../support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md b/.../support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
@@ -6,6 +6,6 @@ As a Primary Owner or Owner of a Team or Enterprise plan, you can manage the abi
 
 2. Use the toggle to change the **Rate chats** setting for your organization:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2058292603/75752add0bed6a9f3ab217f01708/CleanShot%2B2026-02-12%2Bat%2B08_55_14-402x.png?expires=1787712300&amp;signature=1a2a0e0f7868ccf0ace4fcc29171ca7ae1c6700da5cb76a107f2ecef166a7326&amp;req=diAiHst3n4dfWvMW1HO4zYGm8iAbEarP085gFtEpvcQmsFH%2FU3b42aLzvizj%0AZDQEaCyvGOz5lEbZWFc%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2058292603/75752add0bed6a9f3ab217f01708/CleanShot%2B2026-02-12%2Bat%2B08_55_14-402x.png?expires=1787727600&amp;signature=5cd2706c1c60f4cee7a4aa9569619b118f36068807eec871d3a5014ef744aee5&amp;req=diAiHst3n4dfWvMW1HO4zYGm8iAbEq%2FK085gFtEpvcTnatKn%2Bi42ZwYUmXcf%0AKihyj453YJUehBqIfjQ%3D%0A)
 
 More information on how Anthropic collects, uses, and stores feedback data can be found in our Privacy Center: **[How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)**
diff --git a/content/support/10504853-manage-user-feedback-settings-on-claude-console.md b/content/support/10504853-manage-user-feedback-settings-on-claude-console.md
@@ -8,6 +8,6 @@ To manage feedback for your Console organization:
 
 2. Toggle the feedback switch on or off.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1729186182/ebf4032a12a8c56959ca927726ce/Screenshot+2025-09-16+at+12_32_31%E2%80%AFPM.png?expires=1787712300&amp;signature=73f3416caa656ef0bd911ab3af76d127c6ee82b6e767fa025fd0ce349ac92f16&amp;req=dSclH8h2m4BXW%2FMW1HO4zVpN5HAaWGpGJ%2FadMup7FQfFtcJac0wz7MUFNlm%2F%0A%2FQcEVd8Y17oM7c03bCM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1729186182/ebf4032a12a8c56959ca927726ce/Screenshot+2025-09-16+at+12_32_31%E2%80%AFPM.png?expires=1787727600&amp;signature=8ae4a9e8cb2810ef46a60cb8ae193807d61c8fe7bad9abecd1b4e1f8dd838acf&amp;req=dSclH8h2m4BXW%2FMW1HO4zVpN5HAaW29DJ%2FadMup7FQdW73QRc38Mg1xKjrPC%0A4WuWGvfbPSLNdAY5eec%3D%0A)
 
 More information on how Anthropic collects, uses, and stores feedback data can be found in our Privacy Center: [How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)