# Model Context Protocol moves to two releases a year, next due March 30, 2027

> MCP specification releases move to a regular six-month schedule, with the next version targeted for March 30, 2027 and proposal deadlines published in advance.

- Status: official (From the company, authors or authority themselves, with a link to their own page.)
- Topic: Open Source
- Published: 2026-11-11T09:00:00+00:00
- Updated: 2026-11-11T20:08:46.929900+00:00
- Web page: https://ai-news.ikangai.com/story/model-context-protocol-moves-to-two-releases-a-year-next-due-march-30-2027/
- Seen in: Model Context Protocol
- Change: other (Other)
- Applies to: MCP version 2027-03-30

## What changed

MCP specification releases move from the previous schedule to two releases a year on a regular six-month cycle, with the next version targeted for March 30, 2027.

The Model Context Protocol project is moving its specification to two releases a year on a regular six-month cycle. The next version is already targeted: MCP version 2027-03-30, targeted for March 30, 2027. The project said specification releases will generally be published on the last Tuesday of March and September. Proposal deadlines and SDK beta dates will be published alongside each release date so implementers can plan backward from them.

Under the new rules, a proposal that isn't ready moves to a later release rather than pushing the whole specification back. According to the project, authors of a deferred proposal can keep working without rushing, while everyone else keeps preparing for the release they planned around. If an SDK is late, the project will document that gap without moving the specification release date.

The cycle runs on a sequence of freezes. Planning starts eight months before a release. Core Maintainer reviews run from six months out until a soft freeze at two and a half months, when every proposal going into the release must be marked Final and merged. From soft freeze to hard freeze, only fixes, polish, and clarifications within existing scope are accepted. New features and substantial redesigns are not. Tier 1 SDK betas arrive one and a half months before release. A hard freeze begins one month out, when only critical security fixes or fixes for release-blocking correctness or interoperability defects can enter the spec, approved by a full Core Maintainer vote. The project's reasoning is that the soft freeze gives SDK maintainers a settled set of changes to implement, and the betas let client and server developers test those implementations together before the final month of checks.

Because planning for each release starts eight months out and releases come every six months, planning for one release overlaps the last two months of work on the previous one. The March 2027 cycle is an exception, since some of its planning concluded earlier, in August 2026. The governing document, SEP-3398, was written by Kurtis Van Gent and says the proposed transition moves the December 2026 release target to late March 2027. The SEP says release managers confirm exact dates in each cycle's published calendar, while the blog post says the specification 'generally' ships on those Tuesdays. The post does not give the proposal deadlines or SDK beta dates for the March 2027 release. It says those will be published with the release date.

The project says the change affects how releases are prepared, not the protocol itself. MCP messages and version negotiation are unchanged, and specification versions will continue to use dates. Existing clients and servers therefore need no changes because of this announcement.

The project is also formalizing a Release Manager role to coordinate the many parties involved: proposal authors, Working Groups, and the maintainers of several SDKs. Luca Chang joins Den Delimarsky and David Soria Parra as a Release Manager for the next cycle. The project describes the job as tracking work across teams, spotting when one team is waiting on another, and resolving problems before a deadline. Chang co-authored the original Tasks proposal, which introduced experimental support for long-running work in the November 2025 specification. He then worked with Caitie McCaffrey on the Tasks extension. He co-leads the Tasks and Events Working Group and facilitates the Agents Interest Group. The Core Maintainers will still decide which proposals are accepted into each release.

SEP-3398 was accepted by a Core Maintainer vote, which a GitHub comment recorded as 7/7, on October 14, 2026, and merged on October 27. The SEP states that queue placement guarantees neither review time nor release inclusion. Acceptance alone does not meet the soft freeze cutoff.

## Why it matters

Teams building on MCP can plan proposals, SDK upgrades, and testing against fixed dates instead of informal meeting notes. The schedule also means features that miss a deadline will wait six months.

## What you can do

Teams that depend on MCP can note the March 30, 2027 target and the soft freeze and beta dates in their planning, then test SDK betas when they arrive.

## Original source

- [A More Predictable Release Cycle for MCP | Model Context Protocol Blog](https://blog.modelcontextprotocol.io/posts/mcp-release-cycle/)
- [SEP-3398: Release Cycle Updates - Model Context Protocol](https://modelcontextprotocol.io/seps/3398-release-cycle-updates)
- [SEP-3398: Release Cycle Updates by kurtisvg · Pull Request #3398 · modelcontextprotocol/modelcontextprotocol · GitHub](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398)

---

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it.

Cite as: IKANGAI AI News, "Model Context Protocol moves to two releases a year, next due March 30, 2027", 2026-11-11, https://ai-news.ikangai.com/story/model-context-protocol-moves-to-two-releases-a-year-next-due-march-30-2027/
