Enterprises adopting MCP usually start with the core: clients, servers, tools and resources. Within months, requests arrive for more: interactive interfaces inside the chat, single sign-on instead of per-server logins, machine-to-machine access for batch agents, conventions for regulated data. MCP's answer to all of these is extensions. Understanding how they work is now part of designing an agent platform.
Core, projects and extensions
The MCP maintainers describe the ecosystem in three layers1:
- The core specification: how clients and servers talk, and the minimum bar for interoperability.
- Projects: supporting infrastructure such as the Registry for discovering servers and the Inspector for testing.
- Extensions: optional patterns for specialised needs, built on top of the core.
Extensions are strictly additive. They are negotiated during the initialisation handshake, and a client or server that doesn't recognise one simply skips it, so the baseline protocol keeps working12. They are also how future protocol changes get validated: an extension that gains traction signals what might belong in the core1.
What exists today
| Category | Examples | Why an enterprise cares |
|---|---|---|
| UI | MCP Apps, the first official extension, for interactive interfaces in the conversation1 | Richer workflows; new security review surface. See MCP Apps and tool annotations |
| Authorisation | OAuth Client Credentials for machine-to-machine access, and Enterprise-Managed Authorization for central identity provider control13 | Central policy, audit and onboarding through your identity provider |
| Domain conventions | Community groups exploring, for example, compliance metadata for financial services1 | Shared semantics for regulated workflows, once mature |
The maintainers also draw a useful line: proprietary client features that happen to use MCP are not necessarily extensions, and they encourage implementers to adopt extensions as the standard way to add custom behaviour1.
Prefer official extensions over client-specific features. The first works across clients you'll adopt next year; the second ties your workflows to one vendor.
How I decide which to adopt
- Is it official, recommended or community-defined? Official extensions live in the MCP organisation and go through the SEP process5. Community extensions can be valuable but carry more change risk.
- Which of our clients support it? Check the extension support matrix4 against the clients your organisation actually uses. An extension supported by one client only is a pilot, not a standard.
- What's the security impact? UI extensions run code from servers inside hosts; auth extensions change who can access what. Both need review before approval.
- Does it degrade gracefully? Because extensions are optional, test what happens when a client doesn't support one. The workflow should still be safe, even if less convenient.
- Who owns it internally? Each supported extension needs an owner on the platform team, a version policy and a place in your server review checklist.
Auth extensions first
If you adopt one extension category first, make it authorisation. Per-user, per-server OAuth doesn't scale in an enterprise, and machine-to-machine agents need a supported way to authenticate without a person in the loop. Centralising access through your identity provider gives you consistent policy and one audit trail, which supports the controls in securing MCP servers and the evidence expected in SOC 2.
Contributing back
Organisations in regulated sectors have a real opportunity here. If your industry needs shared conventions, such as provenance, consent or compliance metadata on tool calls, the SEP process offers an Extensions Track for proposing them5. Defining those conventions openly is better than every vendor inventing its own.
How I can help
I design enterprise MCP platforms, including extension policy, identity integration and server governance, so agent capabilities can grow without fragmenting. See my AI architecture work, or analyse your challenge and bring the result to a call.
- 1Understanding MCP extensionsModel Context Protocol blog · 11 Mar 2026
- 2Extensions overviewModel Context Protocol documentation
- 3Authorization extensions overviewModel Context Protocol documentation
- 4Extension support matrixModel Context Protocol documentation
- 5SEP guidelinesModel Context Protocol