MCP moves to two spec releases a year, next one due March 30, 2027
The Model Context Protocol's maintainers set a six-month release schedule with fixed freezes and SDK betas. The December 2026 target moves to late March 2027.
Key takeaways
- MCP specification releases will generally come out twice a year, on the last Tuesday of March and of September.
- The next release is targeted for March 30, 2027, replacing the earlier December 2026 target.
- Each cycle runs eight months, with a soft freeze 2.5 months before release and a hard freeze one month before.
- Tier 1 SDK betas are due 1.5 months before each release, and late proposals move to a later release instead of delaying it.
- A new Release Manager role coordinates each cycle; Luca Chang joins the release managers for the next one.
The Model Context Protocol (MCP), the open standard for connecting AI applications to tools and data, will publish new versions of its specification on a regular six-month schedule, its maintainers announced in a post on the official MCP blog. Releases will generally land on the last Tuesday of March and of September. The next one is targeted for March 30, 2027, and the blog says it will be numbered 2027-03-30.
The change is set out in SEP-3398, "Release Cycle Updates," a process proposal written by Kurtis Van Gent, who also sponsored it on behalf of the Core Maintainers. The proposal's own record shows it was accepted on Oct. 14. According to the SEP, the switch pushes the release that had been planned for December 2026 back to late March 2027, subject to confirmation in a transition calendar, after which the regular cadence begins.
Why change the release process?
The maintainers wrote that contributors had to piece together a schedule from meeting notes and GitHub threads. Proposal authors need to know when reviews will happen, they said, and SDK maintainers need to know when the specification will stop changing. The SEP states that the existing proposal rules covered review and acceptance but did not tie those steps to a recurring calendar. According to the blog, the Core Maintainers worked through the plan together at MCPCon Europe.
How will each release cycle work?
Each release has an eight-month cycle, so planning for one release overlaps with the last two months of the previous one. The SEP lists these milestones, counted back from release day:
- 8 months before: planning begins, with feedback from maintainers and Working Groups.
- 6 months before: Core Maintainer reviews of proposals open.
- 2.5 months before: soft freeze. Proposals for the release must be marked Final and merged. From then until hard freeze, only fixes and clarifications within their scope are accepted.
- 1.5 months before: betas of the Tier 1 SDKs arrive for testing.
- 1 month before: hard freeze. According to the blog, only emergency changes can then go in, meaning critical security fixes or fixes for defects that would block the release, and each needs approval from a full Core Maintainer vote.
A proposal that is not ready moves to a later release instead of delaying the whole specification, the maintainers said. If an SDK is late, the blog says the gap will be documented without moving the release date. The blog notes that the March 2027 cycle is a little different because some of its planning already concluded in August.
Who manages the releases?
The process adds a Release Manager role. According to the SEP, each release has a primary and a secondary release manager, who self-nominate and are approved by more than half of all eligible Core Maintainers; the secondary for one cycle becomes primary for the next. Release managers coordinate schedules, track scope and handle communication, while decisions on accepting proposals stay with the Core Maintainers.
The blog post says Luca Chang will join the post's author and David as release managers for the next specification cycle, so three are named for that cycle. It describes him as a co-author of the original Tasks proposal, which brought experimental handling of long-running jobs into the specification released in November 2025, and as co-lead of the Tasks and Events Working Group.
The SEP also requires the release managers to publish a retrospective after the first release under the new process. It is to cover queue wait times, readiness at soft freeze and SDK beta availability, among other points.
What does this mean for developers?
For teams that build MCP clients and servers, the schedule gives fixed points to plan around: scope is fixed at soft freeze, after hard freeze only emergency fixes approved by a full Core Maintainer vote can go in, and SDK betas arrive before release. The maintainers asked the community to test the betas with the clients and servers they already run, so bugs can still be fixed before release day.
This article is based on the MCP project's own blog post and the SEP-3398 document. NextFish found no independent news coverage of the change at the time of writing.
Questions readers are asking
When is the next MCP specification release?
The maintainers are targeting March 30, 2027, and say the version will be numbered 2027-03-30.
How often will MCP be updated?
Twice a year. SEP-3398 says releases will generally fall on the last Tuesday of March and of September.
What happens to a proposal that misses the deadline?
It moves to a later release. The maintainers say the release date will not move to wait for it.
What is the soft freeze?
The point 2.5 months before release when every proposal for that release must be Final and merged; until hard freeze, only fixes and clarifications within its scope are accepted.
Sources
- #model-context-protocol
- #mcp
- #specification
- #open-standards
- #ai-agents
Get the day's top AI & tech stories on WhatsApp: Follow the NextFish channel
Get stories like this every morning.
Related
Agents3 min
OpenAI launches ChatGPT Wallet so its dots agents can buy for users
The payment feature starts with US ChatGPT Pro subscribers. Users approve each purchase with a biometric check, and agents get a payment token, not the real card number.
AnalysisAgents3 min
How big shopping and travel sites now write rules for AI agents
eBay, Target, Booking, Delta and Shopify have all added terms about AI agents. NextFish compared their terms with archived copies to see what changed and when.
Agents3 min
OpenAI's ChatGPT Wallet lets its dots agents buy things for users
Built with American Express, Mastercard and Visa, it starts with some US ChatGPT Pro users. Each purchase needs user approval, and OpenAI says agents never see card details.
Agents2 min
Anthropic lets companies self-host its Claude Managed Agents service
A private beta lets customers run the agent server, database and tool workers in their own cloud or data center. Model calls still go to an outside provider.