blog.modelcontextprotocol.io
The 2026 MCP Roadmap | Model Context Protocol Blog
Excerpt
We spent the last few months working through a long list of candidate priorities. They were informed by production experience, community feedback, and the pain points that keep surfacing. We narrowed them down to the areas that matter most for 2026. ... Right now, every SEP requires full Core Maintainer review, regardless of domain. That’s a bottleneck. It slows down Working Groups that already have the expertise to evaluate proposals in their own area. The goal is to remove that bottleneck without sacrificing quality. ... Enterprises are deploying MCP and running into a predictable set of problems: audit trails, SSO-integrated auth, gateway behavior, and configuration portability. This is also the least defined of the four priorities, and that’s intentional.
Related Pain Points
Slow Maintainer Response and PR Review Bottleneck
8The FastAPI maintainer (@tiangolo) is a bottleneck for development; most PRs go months without response, require extensive rework, or remain unmerged despite being high-quality. No delegation of merge permissions limits community contribution.
Enterprise Deployment Requirements Not Well-Defined
7Enterprises deploying MCP face a predictable set of problems including audit trails, SSO-integrated auth, gateway behavior, and configuration portability. These requirements are poorly defined and understood.