modelcontextprotocol/experimental-ext-triggers-events
Watch
1
0
Fork
You've already forked experimental-ext-triggers-events
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Mirror of https://github.com/modelcontextprotocol/experimental-ext-triggers-events — Incubation space for the MCP Triggers & Events Working Group
13 commits 1 branch 0 tags 136 KiB
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Peter Alexander 567be29eb9
 Consolidate event error codes into reusable general-purpose set 
Replace the seven event-specific error codes (-32011..-32017) with five
general-purpose codes that carry their specifics in a typed `data` payload:

  NotFound, Forbidden, ResourceExhausted, Unsupported, CallbackEndpointError

Bad or non-https callback URLs and malformed secrets now fold into the
standard InvalidParams (-32602). The remaining codes are contiguous
(-32011..-32015) and named for reuse across the protocol rather than scoped
to events; clients still distinguish every case they act on by code, by
method, or by a typed `data` discriminator.

Also corrects the stale -32002 ResourceNotFound reference (no longer present
in the schema) and records the trade-off in Key Design Decisions.
2026-05-22 13:45:50 +01:00
.github Initial commit: WG scaffolding (README, CONTRIBUTING, LICENSE, CODEOWNERS) 2026-04-09 16:53:28 +01:00
docs Consolidate event error codes into reusable general-purpose set 2026-05-22 13:45:50 +01:00
.gitignore Initial commit: WG scaffolding (README, CONTRIBUTING, LICENSE, CODEOWNERS) 2026-04-09 16:53:28 +01:00
CONTRIBUTING.md Initial commit: WG scaffolding (README, CONTRIBUTING, LICENSE, CODEOWNERS) 2026-04-09 16:53:28 +01:00
LICENSE Initial commit: WG scaffolding (README, CONTRIBUTING, LICENSE, CODEOWNERS) 2026-04-09 16:53:28 +01:00
README.md Initial commit: WG scaffolding (README, CONTRIBUTING, LICENSE, CODEOWNERS) 2026-04-09 16:53:28 +01:00

README.md

Triggers & 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.

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.

See the full Working Group Charter for scope, authority, and operations.

Scope

In Scope

  • Specification work: SEPs defining the trigger/callback mechanism, subscription lifecycle, delivery semantics, and event ordering guarantees
  • Reference implementations: SDK components demonstrating server-initiated notifications and client-side callback handling
  • Cross-cutting concerns: Coordination with the Transports WG on transport-specific delivery behavior, and with the Agents WG where task completion notifications intersect with event triggers
  • Documentation: Specification sections covering event-driven patterns and migration guidance from polling-based approaches

Out of Scope

  • Changes to the transport wire format or session model (owned by the Transports WG)
  • General-purpose pub/sub infrastructure beyond what the MCP protocol requires
  • Modifications to existing notification primitives (notifications/resources/updated, notifications/tools/list_changed, etc.) that do not relate to proactive server-initiated delivery

Related Groups

Group Overlap
Transports WG Delivery and ordering guarantees depend on transport capabilities; callback semantics must be coherent across stdio, Streamable HTTP, and future transports
Agents WG SEP-1686 (Tasks) identifies webhook-style task completion notifications as a future consideration; this WG owns that mechanism

Leadership

Role Name Organization GitHub
Lead Clare Liguori Amazon Web Services @clareliguori
Lead Peter Alexander Anthropic @pja-ant

Repository Contents

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