MCP's Agents group is now an interest group. Tasks and Events has its own working group.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On 20 October 2026 the MCP specification repository merged PR 3440. It renames the Triggers and Events working group to Tasks and Events, moves the Tasks scope into it, and converts the Agents working group to an interest group. The Agents charter says the group will recommend how to evolve the protocol, create extensions or document how existing primitives should be used.
Why it matters
If you build agent-backed servers, two groups now split the work. One stabilizes Tasks and owns the protocol surface. The other collects use cases and recommends.
What to do
Read the two charters before you design a long-running agent tool, and follow the Tasks and Events group for the path of Tasks into the core protocol.

My take
Lior Aharonov
Founder, 7IT Solutions
Interest groups talk. Working groups ship. Know which one your feature depends on.
Sources
| modelcontextprotocol PR 3440: Form the Tasks and Events Working Group | github.com |
| Tasks and Events Charter (MCP specification repository) | github.com |
| Agents Charter (MCP specification repository) | github.com |
Researched with AI tools; every fact is checked against the linked sources.