Extensions Overview changedextensions/overview
Nearest release: v2.1.271, published 22 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 13 Sep 2026 21:30 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 24 Oct 2026 11:07 UTC.
Upstream edited
Recorded here
Lines+14added
Lines−14removed
From line
6
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits9to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77MCP extensions are optional additions to the specification that define capabilities beyond the core protocol. Extensions enable functionality that may be modular (e.g., distinct features like authentication), specialized (e.g., industry-specific logic), or experimental (e.g., features being incubated for potential core inclusion).
88
9Extensions are identified using a unique *extension identifier* with the format: `{vendor-prefix}/{extension-name}`, e.g. `io.modelcontextprotocol/oauth-client-credentials`. Identifiers follow the same rules as [`_meta` keys](/specification/draft/basic/index#meta), with a mandatory prefix. Official extensions use the `io.modelcontextprotocol` vendor prefix.
9Extensions are identified using a unique *extension identifier* with the format: `{vendor-prefix}/{extension-name}`, e.g. `io.modelcontextprotocol/oauth-client-credentials`. Identifiers follow the same rules as [`_meta` keys](https://modelcontextprotocol.io/specification/draft/basic/index#meta), with a mandatory prefix. Official extensions use the `io.modelcontextprotocol` vendor prefix.
1010
1111> [!TIP]
1212>
from line 25
2525
2626| Extension | Description |
2727| - | - |
28| [OAuth Client Credentials](/extensions/auth/oauth-client-credentials.md) | OAuth 2.0 client credentials flow for machine-to-machine authentication. |
29| [Enterprise-Managed Authorization](/extensions/auth/enterprise-managed-authorization.md) | Framework for enterprise environments requiring centralized access control. |
28| [OAuth Client Credentials](https://modelcontextprotocol.io/extensions/auth/oauth-client-credentials.md) | OAuth 2.0 client credentials flow for machine-to-machine authentication. |
29| [Enterprise-Managed Authorization](https://modelcontextprotocol.io/extensions/auth/enterprise-managed-authorization.md) | Framework for enterprise environments requiring centralized access control. |
3030
3131### MCP Apps
3232
from line 36
3636
3737| Extension | Description |
3838| - | - |
39| [MCP Apps](/extensions/apps/overview.md) | Allows MCP Servers to display interactive UI elements (charts, forms, video players) inline within conversations |
39| [MCP Apps](https://modelcontextprotocol.io/extensions/apps/overview.md) | Allows MCP Servers to display interactive UI elements (charts, forms, video players) inline within conversations |
4040
41To get started building MCP Apps, see the [quickstart guide](/extensions/apps/build.md#getting-started) or read the full [MCP Apps documentation](https://apps.extensions.modelcontextprotocol.io/api/documents/Quickstart.html).
41To get started building MCP Apps, see the [quickstart guide](https://modelcontextprotocol.io/extensions/apps/build.md#getting-started) or read the full [MCP Apps documentation](https://apps.extensions.modelcontextprotocol.io/api/documents/Quickstart.html).
4242
4343### MCP Tasks
4444
4545| Extension | Description |
4646| - | - |
47| [MCP Tasks](/extensions/tasks/overview.md) | Asynchronous task execution for long-running operations, with polling, mid-flight input, and durable handles. |
47| [MCP Tasks](https://modelcontextprotocol.io/extensions/tasks/overview.md) | Asynchronous task execution for long-running operations, with polling, mid-flight input, and durable handles. |
4848
4949### Skills over MCP
5050
from line 54
5454
5555| Extension | Description |
5656| - | - |
57| [Skills over MCP](/extensions/skills/overview.md) | Discover workflow instructions and read supporting files through MCP resources. |
57| [Skills over MCP](https://modelcontextprotocol.io/extensions/skills/overview.md) | Discover workflow instructions and read supporting files through MCP resources. |
5858
59See the [Skills overview](/extensions/skills/overview.md) to get started and the
60[client matrix](/extensions/client-matrix.md) for implementation support.
59See the [Skills overview](https://modelcontextprotocol.io/extensions/skills/overview.md) to get started and the
60[client matrix](https://modelcontextprotocol.io/extensions/client-matrix.md) for implementation support.
6161
6262## Experimental Extensions
6363
64Experimental extensions provide an incubation pathway for [Working Groups and Interest Groups](/community/working-interest-groups.md) to prototype ideas and collaborate on extension concepts before formal SEP submission.
64Experimental extensions provide an incubation pathway for [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md) to prototype ideas and collaborate on extension concepts before formal SEP submission.
6565
6666Experimental extension repositories live within the MCP GitHub organization with the `experimental-ext-` prefix (e.g., `experimental-ext-interceptors`).
6767
from line 69
6969
7070* Every experimental extension needs to be associated with a Working Group or Interest Group
7171* Repositories and published packages need to clearly indicate their experimental status (e.g., in the README and package name)
72* [Core Maintainers](/community/contributor-ladder.md#core-maintainer) retain oversight of experimental extension repositories, including the ability to archive or remove them
72* [Core Maintainers](https://modelcontextprotocol.io/community/contributor-ladder.md#core-maintainer) retain oversight of experimental extension repositories, including the ability to archive or remove them
7373
7474### Graduation to Official Status
7575
from line 77
7777
7878## Creating Extensions
7979
80The lifecycle for official extensions follows a SEP-based process. For full details, see [SEP-2133: Extensions](/seps/2133-extensions.md).
80The lifecycle for official extensions follows a SEP-based process. For full details, see [SEP-2133: Extensions](https://modelcontextprotocol.io/seps/2133-extensions.md).
8181
821. **Propose**: Create a SEP in the main MCP repository using the [standard SEP guidelines](/community/sep-guidelines.md) with type **Extensions Track**.
821. **Propose**: Create a SEP in the main MCP repository using the [standard SEP guidelines](https://modelcontextprotocol.io/community/sep-guidelines.md) with type **Extensions Track**.
83832. **Implement**: Build at least one reference implementation in an official SDK — this is required before the SEP can be reviewed.
843. **Review**: [Core Maintainers](/community/contributor-ladder.md#core-maintainer) review the SEP and have final authority over inclusion.
843. **Review**: [Core Maintainers](https://modelcontextprotocol.io/community/contributor-ladder.md#core-maintainer) review the SEP and have final authority over inclusion.
85854. **Publish**: Once approved, open a PR to add the extension to the extension repository.
86865. **Adopt**: After that, other clients, servers, and SDKs can implement the extension too.
8787
No line in this hunk matches that.