Incubation space for the MCP Triggers & Events Working Group
by modelcontextprotocolLast 12 weeks · 1 commit
5 of 6 standards met
Motivation and Context Introduces a draft proposal explaining how Tasks and Events can integrate with each other to support intermediate result delivery. Intended to spur discussion for now. This SEP extends (defined by SEP-2663) with an optional field that associates a task with an event stream from the MCP Events primitive. A client that receives a containing subscribes to the named event using the provided input parameters, receiving intermediate results routed to the model while the task executes in the background. The server terminates the event stream when the task reaches a terminal status. 🤖 Generated by cajoling Claude Code into writing something sensible.
Repository: modelcontextprotocol/experimental-ext-triggers-events. Description: Incubation space for the MCP Triggers & Events Working Group Stars: 10, Forks: 4. License: Apache-2.0. Open PRs: 2, open issues: 0. Last activity: 2w ago. Community health: 100%. Top contributors: pja-ant.