# MCP moves to two spec releases a year, next one targeted for March 30, 2027

Canonical: https://theagenticweekly.com/news/model-context-protocol-a-more-predictable-release-cycle-for-mcp · Evidence: Reported · First seen: 2026-11-11 19:36 UTC · Source published: 2026-11-11 09:00 UTC · Brief published: 2026-11-12 08:06 UTC · Updated: 2026-11-12 08:06 UTC · Author: Agentic Weekly

> The Model Context Protocol maintainers said on Nov 11, 2026 that spec releases move to a regular six-month schedule, generally the last Tuesday of March and September. The next release is targeted for March 30, 2027 as version 2027-03-30, and existing clients and servers need no changes.

## What changed

- MCP specification releases move to a regular six-month schedule, generally published on the last Tuesday of March and September, with proposal deadlines and SDK beta dates shared alongside each release date.
- The next release is targeted for March 30, 2027 and will be MCP version 2027-03-30; spec versions keep using dates, and a proposal that is not ready moves to a later release instead of delaying the spec.
- A soft freeze two and a half months before release requires every included proposal to be marked Final and merged; after that only fixes, polish and clarifications within scope are accepted, and no new features.
- Tier 1 SDK betas supporting the frozen spec arrive one and a half months before release, and a hard freeze one month out allows only critical security or release-blocking correctness and interoperability fixes, approved by a full Core Maintainer vote.
- Tier 1 SDKs need stable support before release day; if an SDK is late, the maintainers say they will document the gap rather than move the specification date.
- A formal Release Manager role is created to track proposal and SDK work across the project, while the Core Maintainers still decide which proposals are accepted.

## The regular cycle, as the maintainers describe it

The post lays out the schedule relative to each release date. It also says the March 2027 release is a little different because some of its planning already concluded in August 2026, so these offsets describe the cycles after it; we have not converted them into calendar dates for March 2027.

Regular MCP spec cycle, relative to release day (per the MCP blog)

| When | What happens |
| --- | --- |
| 8 months before | Planning begins with feedback from maintainers and Working Groups |
| 6 months before | Core Maintainer reviews begin and run until soft freeze |
| 2.5 months before | Soft freeze: included proposals must be Final and merged |
| 1.5 months before | Tier 1 SDK betas with support for the frozen spec |
| 1 month before | Hard freeze: only critical security or release-blocking fixes, by full Core Maintainer vote |
| Release day | Spec, release notes and implementation guidance; Tier 1 SDKs stable beforehand |

## What it means for builders (our reading)

- Because planning takes eight months and releases come every six, the post says planning for the next release overlaps the final two months of the current one, so there is always a next window for a proposal that misses a freeze.
- Teams shipping MCP servers or clients get a predictable testing window: the SDK beta period between the 1.5-month mark and release day is when the maintainers ask the community to try betas against the clients and servers they already run.
- The post says this changes release preparation, not MCP messages or version negotiation, so nothing in an existing client or server has to change because of the announcement.

## In the source's words

> "Specification versions will continue to use dates."
> (Model Context Protocol blog, release cycle announcement, https://blog.modelcontextprotocol.io/posts/mcp-release-cycle/)

> "For the next release, we’re targeting March 30, 2027"
> (Model Context Protocol blog, release cycle announcement, https://blog.modelcontextprotocol.io/posts/mcp-release-cycle/)

## What we have not verified

- We did not read the underlying release-cycle proposal (SEP-3398) itself; the schedule here is taken from the blog post.
- The post does not publish the proposal deadlines or SDK beta dates for the March 30, 2027 release; we have not seen them.
- The post does not list which SDKs count as Tier 1, and we have not checked the SDK tiering docs for this brief.

## Timeline

- Source published: 2026-11-11 09:00 UTC
- First seen by our watcher: 2026-11-11 19:36 UTC (via Model Context Protocol blog)
- Brief published: 2026-11-12 08:06 UTC

## Sources

- [Model Context Protocol blog: A More Predictable Release Cycle for MCP](https://blog.modelcontextprotocol.io/posts/mcp-release-cycle/) (primary source) (fetched 2026-11-12)

## Related

- [All news briefs](https://theagenticweekly.com/news)
- [New AI models this week](https://theagenticweekly.com/models/this-week)

## How to cite

Agentic Weekly, "MCP moves to two spec releases a year, next one targeted for March 30, 2027", published 2026-11-12 08:06 UTC, https://theagenticweekly.com/news/model-context-protocol-a-more-predictable-release-cycle-for-mcp