Tasks moves to a new Tasks and Events working group

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.

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 extensions field of their capabilities https://modelcontextprotocol.io/extensions/overview negotiation . This list is maintained by the community. If you notice any inaccuracies or would like to add or update information, please submit a pull request https://github.com/modelcontextprotocol/modelcontextprotocol/pulls . Extension overview Support matrix Auth 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 ext-auth repository https://github.com/modelcontextprotocol/ext-auth for the latest implementation status. Adding extension support to your client If you’re building an MCP client and want to implement extension support: 1. 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 2. 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 3. Implement the extension’s protocol requirements 4. Submit a pull request to update this matrix Extensions Overview https://modelcontextprotocol.io/extensions/overview negotiation for details on the capability negotiation mechanism.