Skip to content
The AI Agent Factory

20.1 What an MCP extension is

Approved by
Panaversity ·
8 min read

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.

  1. 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.
  2. 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).
  3. An extension is used only when both lists name it. Luis's AI app shows screens, so he gets the open-invoices screen.
  4. 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.

Two rows compare what each side supports. Top row, Luis's AI app supports screens and skills over MCP. The connector offers screens and skills over MCP. Both name screens, so Luis gets the open-invoices screen. Bottom row, Marco's coding agent supports skills over MCP but no screens. The connector offers the same two. Only one side names screens, so Marco gets the text answer. A note says a missing feature may drop back to plain MCP, but a missing proof of who is calling must be refused. Below, extensions are off by default, and each side must say it supports one.

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

StageWhat may changeWhat you can expect
ExperimentalAnything, at any timeNothing. It may change or disappear
BetaAnything, but breaking changes should be rareReal use is welcome. Breaking changes are written down
StableOnly with a new revision of MCP itselfIts 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

ExtensionNameStageWhat it addsIn this chapter
MCP Appsio.modelcontextprotocol/uiStableScreens inside the chat20.2 to 20.11
Skills over MCPio.modelcontextprotocol/skillsBetaSkills a server shares20.12 and 20.13
Enterprise-Managed Authorizationio.modelcontextprotocol/enterprise-managed-authorizationStableSign-in decided by a company's own identity system20.14
OAuth Client Credentialsio.modelcontextprotocol/oauth-client-credentialsStableSign-in for a program with no person present20.15
Tasksio.modelcontextprotocol/tasksBeta, planned for the coreLong work that a client checks on later20.15
Server CardsIts proposal, SEP-2127BetaA server's details, readable before connectingNot 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?

  1. MCP Extensions Overview, Model Context Protocol, accessed 15 November 2026.↑↑2↑3↑4
  2. Extension Support Matrix, Model Context Protocol, accessed 15 November 2026.↑
Owner
Panaversity