Commit basic structure based on transports WG

This commit is contained in:
Luca Chang 2026-02-24 11:01:57 -08:00
commit 359a592abb
6 changed files with 279 additions and 2 deletions

98
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,98 @@
# Contributing
We welcome contributions from anyone interested in improving agent interactions facilitated by MCP servers!
## Quick Start
1. **Join the community** — Connect on the `#agents-wg` channel in [MCP Discord](https://discord.com/invite/6CSzBmMkjX)
2. **Understand the scope** — Review the [README](./README.md)
3. **Start contributing** — Attend meetings, open issues, or submit PRs
## Ways to Contribute
### Participate in Discussions
- Join biweekly meetings (no approval needed!)
- Engage in Discord conversations
- Comment on GitHub issues and PRs
- Share your experiences
### Submit Proposals
Have an idea for improving how agents are served over MCP? 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 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](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md).
### Antitrust Compliance
Per the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md), discussions must focus on:
- Technical standards and specifications
- 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](./GOVERNANCE.md). Self-nomination is welcome!
## Communication Channels
| Channel | Purpose |
|---------|---------|
| Discord `#agents-wg` | Real-time discussion and Q&A |
| GitHub Issues | Proposals, bugs, and feature requests |
| GitHub Discussions | Longer-form conversations |
| Biweekly Meetings | Synchronous collaboration and decisions |
## Getting Help
- **Discord:** Ask in `#agents-wg`
- **GitHub Issues:** Open an issue with your question
- **Meetings:** Bring questions to the biweekly call
- **Maintainers:** Reach out to maintainers listed in [GOVERNANCE.md](./GOVERNANCE.md)
We're here to help — don't hesitate to ask!

96
GOVERNANCE.md Normal file
View file

@ -0,0 +1,96 @@
# Agents Working Group Governance
The Agents Working Group operates under a lightweight, consensus-driven governance model aligned with the broader MCP community.
## Principles
1. **Open Participation** — Anyone can participate regardless of affiliation
2. **Transparency** — All decisions are documented and publicly accessible
3. **Consensus-Driven** — Maintainers seek agreement; objections prompt discussion
4. **Antitrust Compliance** — All activities follow the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)
5. **Ecosystem Alignment** — Work aligns with broader MCP goals and specifications
## Roles
### Maintainers
Maintainers are responsible for:
- Reviewing and merging pull requests
- Coordinating meetings and setting agendas
- Managing repository and community health
- Making governance decisions
- Representing the working group to the broader MCP community
**Current Maintainers:**
| Name | Organization | GitHub |
|------|--------------|--------|
| Luca Chang | AWS | [@LucaButBoring](https://github.com/LucaButBoring) |
| Peter Alexander | Anthropic | [@pja-ant](https://github.com/pja-ant) |
### Active Contributors
Active contributors regularly participate in discussions, meetings, or code contributions. They:
- Have demonstrated sustained engagement
- May receive triage permissions
- Are recognized in this document
**Current Active Contributors:**
_None yet — get involved!_
### Contributors
Anyone who participates in any way:
- Joining Discord discussions
- Attending meetings
- Opening or commenting on issues
- Submitting pull requests
- Reviewing proposals
No formal approval is needed to become a contributor.
## Decision Making
1. **Proposal** — Ideas are raised via GitHub issues, PRs, or meetings
2. **Discussion** — Open discussion in Discord and GitHub
3. **Consensus** — Maintainers seek agreement; silence implies consent
4. **Objection Resolution** — Objections trigger further discussion until resolved
5. **Documentation** — All decisions are recorded in meeting notes or GitHub
## Becoming a Maintainer
Maintainer status is earned through sustained, high-quality contributions:
1. Demonstrate expertise in related topics
2. Contribute regularly over an extended period
3. Show good judgment in technical discussions
4. Be nominated by an existing maintainer
5. Receive consensus approval from current maintainers
## Meeting Requirements
All meetings must include:
- Published agenda (48+ hours in advance)
- Open attendance for all participants
## Amendments
Governance changes require:
1. Proposal via GitHub issue or PR
2. Community discussion period
3. Maintainer consensus
4. Documented rationale for the change
## Contact
Questions about governance can be directed to:
- The `#agents-wg` Discord channel
- GitHub Issues in this repository
- Current maintainers directly

View file

@ -1,2 +1,82 @@
# agents-wg
Staging grounds for the Agents Working Group
# MCP Agents Working Group
Welcome to the **MCP Agents Working Group** — a collaborative community focused on improving agent interactions facilitated by [Model Context Protocol (MCP)](https://modelcontextprotocol.io) servers.
## Mission
Pending charter backfill.
## Communication
- **Primary Channel:** [MCP Discord](https://discord.com/invite/6CSzBmMkjX) → `#agents-wg`
- **Meetings:** Biweekly, 30 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:** Biweekly
**Day:** Tuesdays at 10:00am PST
**Duration:** 30 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 improving agent interactions facilitated by MCP servers!
- **Join** the `#agents-wg` channel on [MCP Discord](https://discord.com/invite/6CSzBmMkjX)
- **Attend** biweekly 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
Pending charter backfill.
## Repository Structure
```
/
├── README.md # This file - Quick start guide
├── CHARTER.md # Coming soon
├── GOVERNANCE.md # Governance model, roles, and members
├── CONTRIBUTING.md # Contribution guidelines
├── proposals/ # Proposals and specifications
├── docs/ # Guides and documentation
└── meetings/ # Agendas and notes from working group meetings
```
## 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:** `#agents-wg` channel
- **GitHub Issues:** For proposals, questions, and discussions

1
docs/.gitkeep Normal file
View file

@ -0,0 +1 @@
This file will be deleted.

1
meetings/.gitkeep Normal file
View file

@ -0,0 +1 @@
This file will be deleted.

1
proposals/.gitkeep Normal file
View file

@ -0,0 +1 @@
This file will be deleted.