# 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)](https://modelcontextprotocol.io), 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](./CHARTER.md) for detailed scope and processes.**

## Communication

- **Primary Channel:** [MCP Discord](https://discord.com/invite/6CSzBmMkjX) → `#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:** Wednesdays at 1:00pm PT
**Duration:** 60 minutes
**Format:** Virtual

> **Note:** See [meet.modelcontextprotocol.io](https://meet.modelcontextprotocol.io) for meeting links and calendar.

All meetings include:
- Published agenda (48h prior)
- 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](https://discord.com/invite/6CSzBmMkjX)
- **Attend** weekly meetings (no approval needed!)
- **Contribute** by opening issues, submitting PRs, or providing feedback
- **Review** the [CONTRIBUTING guide](./CONTRIBUTING.md) for detailed guidelines

_See [GOVERNANCE.md](./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

## 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:

- **[CONTRIBUTING.md](./CONTRIBUTING.md)** — Detailed contribution guidelines
- **[MCP Code of Conduct](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md)** — Community standards
- **[MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)** — Required compliance

**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

## Related Resources

- [Model Context Protocol](https://modelcontextprotocol.io)
- [MCP Specification](https://spec.modelcontextprotocol.io)
- [MCP GitHub Organization](https://github.com/modelcontextprotocol)
- [MCP Discord Community](https://discord.com/invite/6CSzBmMkjX)
- [MCP Events Calendar](https://meet.modelcontextprotocol.io)

## Contact

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