What's changed
If you build on the Model Context Protocol, you can now put its spec releases in the calendar. On 11 November 2026, lead maintainers Den Delimarsky and David Soria Parra announced that MCP will publish a new specification every six months. Releases will usually land on the last Tuesday of March and the last Tuesday of September.
The rules sit in SEP-3398, "Release Cycle Updates", a Process proposal written by Kurtis Van Gent. It was created on 17 September 2026 and accepted on 14 October. The Core Maintainers first worked out the approach at their Core Maintainer Day during MCPCon Europe, and the SEP writes it down formally.
The release that had been pencilled in for December 2026 now moves to 30 March 2027, which will carry the version string 2027-03-30. The cycle after that targets 28 September 2027. The most recent spec is still 2026-07-28, the large revision that made the protocol stateless and added a formal deprecation policy.
Luca Chang joins Delimarsky and Soria Parra as a release manager for the coming cycle. Release managers keep the calendar, run the review queue and chase blockers. They don't decide which proposals get in. That stays with the Core Maintainers, who vote.
How a cycle runs
Each release gets an eight-month run-up, and the next one starts every six months. That leaves two months where one cycle is finishing while the next is being planned. The SEP counts every milestone in months before release day:
- 8 months out: planning starts. Core Maintainers draft a roadmap and collect priorities from Working Groups and maintainers.
- 6 months out: the Core Maintainer review window opens and scheduled SEP reviews begin.
- 2.5 months out: soft freeze. Any proposal going into the release has to be Final and merged by now, including spec text, schema changes, a changelog entry, a reference implementation and any required conformance tests. Being accepted isn't enough to make the cut.
- 2 months out: planning for the next release begins.
- 1.5 months out: Tier 1 SDKs ship betas that support the frozen spec.
- 1 month out: hard freeze. Changes are only allowed for critical security holes or defects that block correctness or interoperability, and each one needs a full Core Maintainer vote.
- Release day: the dated spec, release notes, migration guidance and an SDK readiness summary are published.
The key rule is that the date stays put. If a proposal isn't finished by soft freeze, it waits for a later cycle and the release goes out on schedule. An accepted proposal that misses the cut keeps its Accepted status, so it doesn't need another vote unless its design changes a lot. Votes stay open for seven days so people in every time zone can take part, and a proposal passes only with yes votes from more than half of all eligible Core Maintainers. A majority of whoever turns up to a meeting won't do.
What it means for your code
Today, nothing. The maintainers say the change covers how releases are prepared, with no new protocol messages, schema changes or changes to version negotiation. Version identifiers still use the YYYY-MM-DD format. Under the current spec, each request states its protocol version, and a server that doesn't support it replies with an error listing the versions it does. Clients can then retry, or call server/discover up front to check.
What matters more is which SDK you're using. The official SDK page puts TypeScript, Python, C#, Go, Rust and Ruby in Tier 1. Java is Tier 2. Swift, PHP and Kotlin are Tier 3. Tier 1 SDKs must pass every applicable conformance test and support new protocol features before a spec ships. Tier 2 SDKs have six months after a release and need an 80 per cent conformance pass rate. Tier 3 has no timeline at all. So if your mobile app uses the Kotlin or Swift SDK, plan on getting new spec features later than TypeScript or Python teams. If an SDK misses its beta or stable milestone, the gap goes into the release guidance, and the spec still ships.
Rough dates for a New Zealand team
The SEP says release managers publish exact UTC deadlines in a transition calendar, and that calendar is the one to trust. Working back from 30 March 2027 using the SEP's offsets gives these rough targets:
- Mid-January 2027: soft freeze for the March release.
- Late January 2027: planning starts for September 2027.
- Mid-February 2027: Tier 1 SDK betas, leaving about two weeks to report problems before hard freeze.
- Late February or early March 2027: hard freeze.
- 30 March 2027: release. A Tuesday in the US is usually already Wednesday here, so expect the announcement on 31 March NZ time.
For local contributors, the soft freeze is the date to watch. It falls just after the summer break, when many teams have been offline since Christmas. If you're helping with a proposal aimed at March, treat early December as your real deadline.
Deprecations now have a likely date
The 2026-07-28 spec deprecated four features. Under MCP's lifecycle policy, each becomes eligible for removal in the first revision released on or after 28 July 2027. On the new calendar, that's the release set for 28 September 2027. Eligible doesn't mean certain: the Core Maintainers decide on removal while preparing a release, and they could leave it later. The registry lists these migration paths:
- Roots: pass directories or files through tool parameters, resource URIs or server configuration.
- Sampling: call LLM provider APIs directly. The
includeContextvalues"thisServer"and"allServers"will go when Sampling does. - Logging: write to
stderron stdio transports and use OpenTelemetry for observability. - OAuth client registration under RFC 7591: move to Client ID Metadata Documents.
The old HTTP+SSE transport is on its own track. It becomes removable three months after SEP-2596 reaches Final, and Streamable HTTP replaces it.
Limits and open questions
The SEP admits some trade-offs. Every SEP type shares the same review window, so a process or extension proposal that's ready outside the window may have to wait. Requiring a majority of all eligible Core Maintainers guards against approvals from a thin meeting, but it also means enough maintainers have to vote before each deadline. The March 2027 cycle is unusual too, because it reuses planning finished in August 2026. Once that release is out, the release managers have promised a retrospective covering queue wait times, readiness at soft freeze, SDK beta availability and emergency changes. That'll be the first real evidence on whether the dates hold.
What builders can do now
- Pin SDK versions and read each SDK's notes on which spec revisions it supports.
- Book time in mid-February to test your clients and servers against the Tier 1 betas. Finding problems before hard freeze is the whole point of the beta window.
- Check your SDK's roadmap. Tier 2 SDKs must publish a plan toward Tier 1, and Tier 1 SDKs must publish a roadmap.
- Start migrating off Roots, Sampling, Logging and RFC 7591 registration now, with the September 2027 release as the earliest point they could disappear.
- Join a Working Group if you've got a proposal in mind. The maintainers say you don't need a finished SEP to start talking, and a Working Group or the Core Maintainers can sponsor it into the review queue once it's ready.
We'll be watching the transition calendar and will update our members once the exact freeze dates are confirmed.
Sources
- A More Predictable Release Cycle for MCP (MCP Blog)
- SEP-3398: Release Cycle Updates
- Versioning (MCP specification)
- Deprecated Features, 2026-07-28 (MCP specification)
- SDK Tiers (MCP community docs)
- SDKs (MCP docs)
- MCP Is Growing Up (Agentic AI Foundation)
- MCP gets an enterprise makeover (The Register)
Build with people working on the same things
Join the Auckland Society for AI: NZ$599 a year with a ForgeBox and the members' projects area. Our Auckland meetups are open to everyone.