20.1 What an MCP extension is
- Approved by
- Panaversity ·
In everyday life. A car is sold with a base model and optional extras: a tow bar, a roof rack, heated seats. The base car drives without any of them. A tow bar only helps if the trailer has the matching hitch.
What you will learn. What an MCP extension is, how two sides agree to use one, what its stage promises, and what to do when the other side does not support it.
Why it matters. Everything in this chapter is an extension: screens, skills that travel with a server, and two new ways to sign in. Each one works only when both sides support it, so a connector that sells must decide what happens when they do not.
One request, start to finish. Luis's AI app connects to Brightline's connector on Tuesday morning.
- The AI app says what it supports. With each request it sends a list of the extensions it can use, such as the screens extension.
- The connector says what it offers, in its answer to
server/discover, the request where an AI app asks a server what it can do (17.1). - An extension is used only when both lists name it. Luis's AI app shows screens, so he gets the open-invoices screen.
- Marco opens the same connector from a coding agent that shows no screens. Its list does not name the screens extension. The connector falls back to plain MCP, and Marco gets the text answer.

Figure 20.3. An extension is used only when both sides name it. A missing screen drops back to text.
What is an extension?
An extension is an optional addition to MCP for features that not every AI app needs. Each has a name with a vendor part, such as io.modelcontextprotocol/ui. Official extensions use the io.modelcontextprotocol prefix. Extensions are always off by default, and each side must turn them on on purpose.1
What does an extension's stage promise?
Every extension is at one of three stages:1
| Stage | What may change | What you can expect |
|---|---|---|
| Experimental | Anything, at any time | Nothing. It may change or disappear |
| Beta | Anything, but breaking changes should be rare | Real use is welcome. Breaking changes are written down |
| Stable | Only with a new revision of MCP itself | Its behavior is fixed within a protocol revision |
Build a product only on Beta or Stable, and record the stage you built on.
Which official extensions are there today?
As of November 15, 2026, the MCP project lists these:1
| Extension | Name | Stage | What it adds | In this chapter |
|---|---|---|---|---|
| MCP Apps | io.modelcontextprotocol/ui | Stable | Screens inside the chat | 20.2 to 20.11 |
| Skills over MCP | io.modelcontextprotocol/skills | Beta | Skills a server shares | 20.12 and 20.13 |
| Enterprise-Managed Authorization | io.modelcontextprotocol/enterprise-managed-authorization | Stable | Sign-in decided by a company's own identity system | 20.14 |
| OAuth Client Credentials | io.modelcontextprotocol/oauth-client-credentials | Stable | Sign-in for a program with no person present | 20.15 |
| Tasks | io.modelcontextprotocol/tasks | Beta, planned for the core | Long work that a client checks on later | 20.15 |
| Server Cards | Its proposal, SEP-2127 | Beta | A server's details, readable before connecting | Not covered |
Which AI apps support which extension changes often. The MCP project keeps a public table of it, the support matrix.2
What if the other side does not support it?
If one side supports an extension and the other does not, the supporting side either falls back to plain MCP or refuses the request with an error, when the extension is required.1 The chapter's rule for choosing:
- Fall back for features. A connector with screens still returns its text answer (20.9). Marco loses the table, not the invoices.
- Never fall back on proof of who someone is. A connector that requires a sign-in extension may refuse an AI app that cannot use it. A missing screen is an inconvenience. A missing sign-in check is a breach.
At work. The builder writes the connector's extension list into docs/connector-spec.md: screens (Stable), with the text answer as the fallback. Ana adds one line: "No extension may change who can see what."
The operating rule: use an extension only when both sides declare it, build on Beta or Stable, fall back to plain MCP for features, and refuse rather than fall back when the extension proves who is calling.
Check yourself
Question 1 / 3
0 answered
Marco opens Brightline's connector from a coding agent that shows no screens. What should he get?
Sources
- Owner
- Panaversity