modelcontextprotocol/transports-wg
Watch
1
0
Fork
You've already forked transports-wg
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
transports-wg/CONTRIBUTING.md
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

3.2 KiB
Raw Blame History

Contributing to the Transports Working Group

We welcome contributions from anyone interested in improving MCP transports!

Quick Start

  1. Join the community — Connect on the #transports-wg channel in MCP Discord
  2. Understand the scope — Review the CHARTER and README
  3. Start contributing — Attend meetings, open issues, or submit PRs

Ways to Contribute

Participate in Discussions

  • Join weekly meetings (no approval needed!)
  • Engage in Discord conversations
  • Comment on GitHub issues and PRs
  • Share your transport implementation experiences

Submit Proposals

Have an idea for improving MCP transports? We'd love to hear it!

  1. Open an issue to discuss the idea first
  2. Draft a proposal following the template in proposals/
  3. Submit a PR for community review
  4. Iterate based on feedback

Improve Documentation

  • Fix typos or clarify existing docs
  • Add examples or guides
  • Document edge cases or gotchas

Review and Provide Feedback

  • Review open PRs
  • Test proposed changes
  • Share implementation feedback

Proposal Development

When developing transport proposals:

  1. Propose first — Open an issue to discuss before writing a full proposal
  2. Follow MCP standards — Align with existing MCP conventions and patterns
  3. Document thoroughly — Include rationale, examples, and edge cases
  4. Consider breadth — Think about applicability across implementations

Promoting Proposals to Core Spec

For proposals with broad applicability:

  1. Gather implementation experience — Get real-world validation
  2. Present to the working group — Build consensus and support
  3. Coordinate with core maintainers — Work with the MCP maintainer liaison
  4. Draft a SEP — Follow the MCP Spec Enhancement Proposal process

Guidelines

Code of Conduct

All participants must follow the MCP Code of Conduct.

Antitrust Compliance

Per the MCP Antitrust Policy, discussions must focus on:

  • Technical standards and specifications
  • Interoperability patterns
  • Open collaboration

And must avoid:

  • Pricing, costs, or margins
  • Customer lists or strategies
  • Competitive information

Recognition

Active contributors — those who attend 2+ meetings or make substantive contributions — can request recognition in GOVERNANCE.md. Self-nomination is welcome!

Communication Channels

Channel Purpose
Discord #transports-wg Real-time discussion and Q&A
GitHub Issues Proposals, bugs, and feature requests
GitHub Discussions Longer-form conversations
Weekly Meetings Synchronous collaboration and decisions

Getting Help

  • Discord: Ask in #transports-wg
  • GitHub Issues: Open an issue with your question
  • Meetings: Bring questions to the weekly call
  • Maintainers: Reach out to maintainers listed in GOVERNANCE.md

We're here to help — don't hesitate to ask!