Reported News
MCP moves to two spec releases a year, next one targeted for March 30, 2027
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.
- Changes reported
- 6
- listed below, each from a source we read
- We tested
- Not tested yet
- reported from sources; we did not run it ourselves
- Gaps we flag
- 3
- things we could not verify
- Sources
- 1
- 1 primary, linked below
What changed
| # | What the source says | Status |
|---|---|---|
| 01 | 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. | Reported |
| 02 | 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. | Reported |
| 03 | 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. | Reported |
| 04 | 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. | Reported |
| 05 | 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. | Reported |
| 06 | 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. | Reported |
reported by the sourcemeasured or run by usnot verified
Primary source: Model Context Protocol blog: A More Predictable Release Cycle for MCP. We are the fast, independent index; the vendor’s own page is the source of record for this release.
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.
| 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.”
“For the next release, we’re targeting March 30, 2027”
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.
This brief is Reported: written from the sources below, not from running the release ourselves.
Sources
- Model Context Protocol blog: A More Predictable Release Cycle for MCPprimary source · fetched 2026-11-12
Related
Spotted an error? See our corrections policy or email the address on the contact page. Markdown version for agents: /news/model-context-protocol-a-more-predictable-release-cycle-for-mcp.md
Want these briefs in your Google Top Stories? Add Agentic Weekly as a preferred source on Google.
Newsletter
The Weekly Verdict. Free, every Monday.
A free email every Monday: the week's few big AI releases, then 5 short use cases for the new models, each with a prompt you can paste.
Free. Double opt-in. One click to unsubscribe.