# Contributing

## How to Participate

This Working Group welcomes contributions from anyone interested in server-initiated notifications and event-driven patterns in MCP. You can participate by:

- Joining discussions in the [#triggers-and-events-wg Discord channel](https://discord.com/channels/1358869848138059966/1479499641304387624) (info on joining the Discord server [here](https://modelcontextprotocol.io/community/communication#discord))
- Opening or commenting on [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) in the main MCP repo
- Sharing experimental findings from your own implementations
- Contributing to proposals and reference implementations

## Communication Channels

| Channel | Purpose | Response Expectation |
| :--- | :--- | :--- |
| [Discord #triggers-and-events-wg](https://discord.com/channels/1358869848138059966/1479499641304387624) | Quick questions, coordination, async discussion | Best effort |
| [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) | Meeting notes, long-form technical proposals, experimental findings | Weekly triage |
| This repository | Living reference for proposals, findings, and reference implementations | Updated after meetings |

## Meetings

The WG holds a weekly 30-minute working session for technical discussion and proposal review. Scheduling is posted in the [#triggers-and-events-wg Discord channel](https://discord.com/channels/1358869848138059966/1479499641304387624).

Meeting norms:

- Agendas published 24 hours in advance
- Notes published within 48 hours

## Decision-Making

As a Working Group, we operate by **consensus** within the scope defined by our [charter](https://modelcontextprotocol.io/community/triggers-events/charter). Spec changes require WG consensus followed by Core Maintainer approval through the SEP process. See the charter's Authority & Decision Rights table for specifics.

## Contribution Guidelines

### Proposals and Findings

When adding experimental findings or new proposals:

- Include enough detail for others to reproduce or evaluate
- Note which clients, servers, and transports were tested
- Be explicit about what worked, what didn't, and what remains untested
- Attribute community input with GitHub handles and link to the source where possible

### Filing Issues

Use GitHub Issues for:

- Proposing new approaches or use cases
- Reporting gaps in documentation
- Tracking action items from meetings