{"slug": "tasks-moves-to-a-new-tasks-and-events-working-group", "title": "Tasks moves to a new Tasks and Events working group", "summary": "The Model Context Protocol community has moved its Tasks work into a new Tasks and Events working group, according to the project's extension documentation. The documentation describes extensions as opt-in, with a client using an extension only when both client and server declare support in the `extensions` field of their capabilities, and directs MCP client builders to declare support in the `io.modelcontextprotocol/clientCapabilities` sent in each request's `_meta` and to read the server's `extensions` from its `server/discover` response. The community-maintained support matrix tracks extension implementations, with Auth extension support (OAuth Client Credentials and Enterprise-Managed Authorization) tracked separately from core MCP authorization features (DCR, CIMD) in the ext-auth repository.", "body_md": "[official extension](https://modelcontextprotocol.io/extensions/overview). Extensions are always opt-in: a client only uses an extension if both client and server declare support in the\n\n`extensions` field of their [capabilities](https://modelcontextprotocol.io/extensions/overview#negotiation).\n\nThis list is maintained by the community. If you notice any inaccuracies or would like to add or update information, please \n\n[submit a pull request](https://github.com/modelcontextprotocol/modelcontextprotocol/pulls).\n## Extension overview\n\n## Support matrix\n\nAuth extension support (OAuth Client Credentials and Enterprise-Managed Authorization) is tracked separately from the core MCP authorization features (DCR, CIMD). Check each extension’s specification and the \n\n[ext-auth repository](https://github.com/modelcontextprotocol/ext-auth)for the latest implementation status.\n## Adding extension support to your client\n\nIf you’re building an MCP client and want to implement extension support:\n1. Review the extension specification (e.g., in the [ext-auth](https://github.com/modelcontextprotocol/ext-auth) or[ext-apps](https://github.com/modelcontextprotocol/ext-apps) repository)\n2. Declare support in the `extensions` field of the`io.modelcontextprotocol/clientCapabilities` your client sends in each request’s`_meta` , and read the server’s`extensions` from its[`server/discover`](https://modelcontextprotocol.io/specification/draft/server/discover) response\n3. Implement the extension’s protocol requirements\n4. Submit a pull request to update this matrix\n\n[Extensions Overview](https://modelcontextprotocol.io/extensions/overview#negotiation)for details on the capability negotiation mechanism.", "url": "https://wpnews.pro/news/tasks-moves-to-a-new-tasks-and-events-working-group", "canonical_source": "https://modelcontextprotocol.io/extensions/client-matrix", "published_at": "2026-10-26 00:00:00+00:00", "updated_at": "2026-10-26 23:41:44.245658+00:00", "lang": "en", "topics": ["agent-protocols", "developer-tools", "ai-agents"], "entities": ["Model Context Protocol", "Tasks and Events working group", "ext-auth", "ext-apps"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/tasks-moves-to-a-new-tasks-and-events-working-group", "markdown": "https://wpnews.pro/news/tasks-moves-to-a-new-tasks-and-events-working-group.md", "text": "https://wpnews.pro/news/tasks-moves-to-a-new-tasks-and-events-working-group.txt", "jsonld": "https://wpnews.pro/news/tasks-moves-to-a-new-tasks-and-events-working-group.jsonld"}}