MCP extensions framework
What it is
The extensions framework is the formal mechanism the Model Context Protocol's
2026-07-28 specification introduced for adding new capabilities to MCP without
touching the core protocol. Extensions get reverse-DNS identifiers, are
negotiated through a capabilities map during session setup, live in their own
ext-* repositories with delegated maintainers, and version independently of
the core spec. It turns what used to be informal, ad hoc additions to MCP into
a governed extension system with a defined lifecycle (Active, Deprecated,
Removed).
Why it's emerging now
MCP's core spec was rewritten to be stateless in the same release, which forced a decision about where non-core features should live. Rather than keep growing the core protocol, the maintainers moved everything that isn't strictly required — interactive UIs, long-running task tracking — out into this extensions system. Two features that already existed as experimental parts of MCP, Apps and Tasks, were the first to migrate into it, which is why they shipped "under" the framework rather than alongside it.
How it relates to what you know
This sits one level above MCP Apps and MCP Tasks, both already on the
ledger: those are the first two extensions built on this framework, not
separate mechanisms. It plays a similar role to how CIMD replaced ad hoc
OAuth client registration — a case of MCP formalizing a pattern that was
previously informal, this time for capability growth rather than identity.