Mirror of https://github.com/modelcontextprotocol/transports-wg — Transports Working Group
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Peter Alexander a67f95ca0f
Initial repository structure for Transports WG
Set up the basic structure for the MCP Transports Working Group, modeled
after the financial-services-interest-group repository.

Files added:
- README.md: Mission, meetings, focus areas, participation guide
- CHARTER.md: Scope, proposal promotion pathway
- GOVERNANCE.md: Roles, decision-making process (maintainers TBD)
- CONTRIBUTING.md: How to participate and contribute
- LICENSE: MIT License
- docs/: Directory for future documentation
- proposals/: Directory for transport proposals/specs

Focus areas:
- Scalability (connection pooling, load distribution)
- Reliability (error handling, reconnection, delivery guarantees)
- Transport Semantics (protocol behavior, message ordering)
- Interoperability (cross-platform compatibility, testing)
2026-01-08 13:15:50 +00:00
docs Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00
proposals Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00
CHARTER.md Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00
CONTRIBUTING.md Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00
GOVERNANCE.md Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00
LICENSE Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00
README.md Initial repository structure for Transports WG 2026-01-08 13:15:50 +00:00

MCP Transports Working Group

Welcome to the MCP Transports Working Group — a collaborative community focused on improving the usability of transports in the Model Context Protocol (MCP), including scalability, reliability, and semantics.

Mission

The Transports Working Group coordinates community stakeholders to:

  • Improve transport usability across MCP implementations
  • Define scalability patterns for connection pooling, load distribution, and resource management
  • Establish reliability standards for error handling, reconnection, and message delivery guarantees
  • Clarify transport semantics for protocol behavior, message ordering, and state management
  • Drive interoperability across platforms and implementations

See the CHARTER for detailed scope and processes.

Communication

  • Primary Channel: MCP Discord → #transports-wg
  • Meetings: Weekly, 60 minutes
    • Meeting agendas posted in Discord ≥48 hours in advance
  • Work Tracking: GitHub Issues and Discussions in this repository
  • Reporting: Regular updates to the broader MCP community

Meetings

Cadence: Weekly Day: Tuesdays at 1:00pm Duration: 60 minutes Format: Virtual

Note: See meet.modelcontextprotocol.io for meeting links and calendar.

All meetings include:

  • Brief antitrust reminder at start
  • Published agenda (48h prior)
  • Public notes with decisions and action items
  • Open attendance for all interested participants

How to Participate

We welcome participation from anyone interested in MCP transports!

  • Join the #transports-wg channel on MCP Discord
  • Attend weekly meetings (no approval needed!)
  • Contribute by opening issues, submitting PRs, or providing feedback
  • Review the CONTRIBUTING guide for detailed guidelines

See GOVERNANCE.md for current members, roles, and how to become a maintainer.

Current Focus Areas

Our work focuses on:

  1. Scalability — Connection pooling, load distribution, resource management
  2. Reliability — Error handling, reconnection strategies, message delivery guarantees
  3. Transport Semantics — Protocol behavior, message ordering, state management
  4. Interoperability — Cross-platform compatibility, testing patterns, conformance

Repository Structure

/
├── README.md                 # This file - Quick start guide
├── CHARTER.md               # Mission, scope, and proposal strategy
├── GOVERNANCE.md            # Governance model, roles, and members
├── CONTRIBUTING.md          # Contribution guidelines
├── proposals/               # Transport proposals and specifications
└── docs/                    # Guides and documentation

Contributing

We welcome contributions of all kinds! Please review:

Quick Start:

  • Open an issue to propose ideas or report problems
  • Submit a PR for proposals, documentation, or improvements
  • Join discussions in Discord or GitHub

Contact

  • Discord: #transports-wg channel
  • GitHub Issues: For proposals, questions, and discussions