MCP Moves to Two Spec Releases a Year, the Next on March 30
MCP's maintainers said Nov. 11 that spec releases now come every March and September, and that late proposals wait for the next one.

Model Context Protocol specification releases will now come out twice a year, generally on the last Tuesday of March and September, lead maintainers Den Delimarsky and David Soria Parra said in a Nov. 11 post on the MCP blog. The next release is set for March 30, 2027, as version 2027-03-30.
A proposal that isn’t ready by its deadline will move to a later release instead of delaying the spec, the post said. The current spec is 2026-07-28, published July 28.
Nothing changes on the wire
The schedule changes how releases are prepared, not MCP messages or version negotiation, so existing clients and servers need no changes, the maintainers wrote. Spec versions will keep using dates as names.
The core maintainers worked out the plan at MCPCon Europe. Kurtis Van Gent wrote it up as SEP-3398, Release Cycle Updates, which the post called “our de facto release guidance moving forward.”
The calendar for each release
Planning for a regular release starts eight months before release day, so the next cycle’s planning overlaps the last two months of the current one. The post laid out these steps:
- Six months out: core maintainer reviews begin.
- Two and a half months out: soft freeze. Every proposal in the release must be marked Final and merged. Fixes and clarifications within scope are still accepted; new features are not.
- Six weeks out: Tier 1 SDK betas ship with support for the frozen spec.
- One month out: hard freeze. Only critical security fixes or fixes for defects that block the release go in, and each needs a full core maintainer vote.
- Release day: the spec and release notes publish. Tier 1 SDKs must have stable support ready beforehand. If an SDK is late, the gap is documented and the date holds.
The March 2027 release won’t follow this exactly, because some of its planning finished in August, the post said.
A new release manager role
Luca Chang will join Delimarsky and Soria Parra as a release manager for the next cycle. The role tracks work across proposal authors, working groups and SDK maintainers and flags when one team is waiting on another. The core maintainers still decide which proposals are accepted.
Chang co-authored the original Tasks proposal, which added experimental support for long-running work in the November 2025 spec, and co-leads the Tasks and Events Working Group, the post said.
Key takeaways
- MCP spec releases now come every six months, on the last Tuesday of March and September.
- The next spec, 2027-03-30, is due March 30, 2027.
- Unready proposals slip to the next release; the date doesn’t move.
- Tier 1 SDK betas arrive six weeks before each release.
- Existing clients and servers need no changes.
The take
We think a fixed date matters more to docs teams than any feature in the next spec. Docs platforms now run MCP servers for the sites they host. ReadMe added OAuth sign-in to its MCP server in its Nov. 5 changelog, GitBook’s Nov. 11 changelog updated the MCP server on published sites and Mintlify’s Nov. 13 changelog changed its admin MCP tools. Each of those servers has to follow the spec when it changes.
Until now, developers had to piece a release schedule together from meeting notes and GitHub threads, the maintainers said. A calendar turns that into a date a team can plan around.
The useful window is the six weeks of SDK betas. That is when the spec is frozen and the SDKs can be tested, and the post asked developers to try the betas against the clients and servers they already run. Bugs found then can still be fixed before release.
We’d put the beta window for each release on the team calendar now and test the docs MCP server against it, rather than waiting for release day.


