The Model Context Protocol (MCP) is shedding its monolithic skin. With the release of the SEP-2133 extensions framework, the project is pivoting from a rigid, all-encompassing specification toward a modular platform model.
The maintainers are effectively narrowing the protocol’s core responsibilities. By deprecating features like Roots, Sampling, and Logging, the project is offloading peripheral concerns to established industry standards like OpenTelemetry. As Angie Jones, VP of Developer Experience at AAIF, put it, “MCP is strongest when it defines the client-server contract clearly and leaves surrounding concerns to the systems that already handle them well.”
To manage this transition, SEP-2133 introduces a formal extensions framework that mirrors the modularity seen in mature software infrastructure. Extensions are categorized into three tracks: Official, Experimental, and Unofficial. To prevent namespace collisions, all extensions must use reverse-DNS identifiers. Breaking changes require a new identifier entirely.
For builders, this framework addresses a persistent friction point: feature discovery. Under the new model, negotiation occurs during the initial handshake, where clients and servers explicitly advertise their supported extensions. The first wave of official extensions includes MCP Apps, MCP Tasks, and MCP Authorization.
However, this increased modularity introduces new security trade-offs. The “State of MCP Security 2026” report from Nimblebrain draws a stark comparison between the current state of the ecosystem and “web security in 2005.” With only 8.5% of the 3,012 surveyed servers currently utilizing OAuth, the industry faces a significant gap between the new Authorization extension’s capabilities and the ecosystem’s actual security posture.
By decoupling peripheral features from the base protocol and creating a governed pathway for new capabilities, the MCP ecosystem is building the structural conditions for sustainable growth. That pattern — a lean core with a governed extension layer — is the same one that made HTTP, Linux, and Kubernetes durable platforms rather than brittle monoliths.