Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

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))
- Joining discussions in the [#tasks-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
Expand All @@ -13,13 +13,13 @@ This Working Group welcomes contributions from anyone interested in server-initi

| Channel | Purpose | Response Expectation |
| :--- | :--- | :--- |
| [Discord #triggers-and-events-wg](https://discord.com/channels/1358869848138059966/1479499641304387624) | Quick questions, coordination, async discussion | Best effort |
| [Discord #tasks-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).
The WG holds a weekly 30-minute working session for technical discussion and proposal review. Scheduling is posted in the [#tasks-events-wg Discord channel](https://discord.com/channels/1358869848138059966/1479499641304387624).

Meeting norms:

Expand All @@ -28,7 +28,7 @@ Meeting norms:

## 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.
As a Working Group, we operate by **consensus** within the scope defined by our [charter](https://modelcontextprotocol.io/community/working-groups/tasks-events). 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

Expand Down
16 changes: 11 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Triggers & Events Working Group
# Tasks and Events Working Group

> ⚠️ **Experimental** — This repository is an incubation space for the Triggers & Events Working Group. Contents are exploratory and do not represent official MCP specifications or recommendations.
> ⚠️ **Experimental** — This repository is an incubation space for the Tasks and Events Working Group. Contents are exploratory and do not represent official MCP specifications or recommendations.

## Mission

The Triggers & Events Working Group exists to define how MCP servers proactively notify clients of state changes. Today, clients learn about server-side updates by polling or holding an SSE connection open. This WG will specify a standardized callback mechanism — webhooks or similar — that lets servers push notifications when new data is available, with defined ordering guarantees that hold across all transports.
The Tasks and Events Working Group exists to define how MCP servers proactively notify clients of state changes. Today, clients learn about server-side updates by polling or holding an SSE connection open. This WG will specify a standardized callback mechanism — webhooks or similar — that lets servers push notifications when new data is available, with defined ordering guarantees that hold across all transports.

See the full [Working Group Charter](https://modelcontextprotocol.io/community/triggers-events/charter) for scope, authority, and operations.
See the full [Working Group Charter](https://modelcontextprotocol.io/community/working-groups/tasks-events) for scope, authority, and operations.

## Scope

Expand Down Expand Up @@ -35,8 +35,14 @@ See the full [Working Group Charter](https://modelcontextprotocol.io/community/t
| Role | Name | Organization | GitHub |
| :--- | :--- | :--- | :--- |
| Lead | Clare Liguori | Amazon Web Services | [@clareliguori](https://github.com/clareliguori) |
| Lead | Peter Alexander | Anthropic | [@pja-ant](https://github.com/pja-ant) |
| Lead | Peter Alexander | - | [@poita](https://github.com/poita) |
| Lead | Luca Chang | Amazon Web Services | [@LucaButBoring](https://github.com/LucaButBoring) |
| Lead | Caitie McCaffrey | Microsoft | [@CaitieM20](https://github.com/CaitieM20) |

## Repository Contents

| Extension | Stage | Specification | SEP |
| :--- | :--- | :--- | :--- |
| Events (`io.modelcontextprotocol/events`) | Beta | [`specification/beta/events/`](specification/beta/events/events.mdx) | [SEP-3415](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/3415-events-extension.md) |

This repository will hold proposals, reference implementations, and experimental findings as the WG's work progresses. See [CONTRIBUTING.md](CONTRIBUTING.md) for how to participate.
Loading