MCP MOVES TO A SIX-MONTH RELEASE SCHEDULE; THE NEXT VERSION IS TARGETED FOR 30 MARCH 2027
WHAT CHANGED
ESTABLISHED: The post on the MCP blog, dated 11 November 2026, says: we're moving MCP specification releases to a regular six-month schedule.
And: We'll generally publish specification releases on the last Tuesday of March and September.
ESTABLISHED: The next date is given as a target: For the next release, we're targeting March 30, 2027 - expect MCP version 2027-03-30 to land then.
ESTABLISHED: The post lists the milestones before each release:
| Time before release | Milestone, as stated |
|---|---|
| Eight months | planning begins |
| Six months | Core Maintainer reviews begin and run until soft freeze |
| Two and a half months | soft freeze: Every proposal going into the spec release must be marked Final and merged. |
| One and a half months | Tier 1 SDK betas arrive with support for the frozen specification. |
| One month | hard freeze: Only critical security fixes or fixes for release-blocking correctness or interoperability defects can go into the spec |
SOURCE AND HOW IT WAS CHECKED
ESTABLISHED: The post was downloaded from blog.modelcontextprotocol.io on 17 November 2026 and each quotation matched to the page text; the page metadata gives the publication time 2026-11-11T09:00:00Z. The draft changelog on modelcontextprotocol.io was read the same day. Both pages are published by the MCP project, so this is a single source.
WHY IT MATTERS
ESTABLISHED: The protocol itself does not change with this announcement. The post says: This changes how we prepare a release, not MCP messages or version negotiation, so there's nothing you need to change in an existing client or server because of this announcement. Specification versions will continue to use dates.
ESTABLISHED: What changes is that the work ahead can be read in advance. On 17 November 2026 the draft changelog, which holds Changes since the most recent release
, listed two items. One updates the referenced OAuth Client ID Metadata Document draft from revision -00 to -03 and says: MCP implementations that support Client ID Metadata Documents MUST follow this version.
The other restores the optional _meta field on five types, which the changelog says was unintentionally dropped in 2026-07-28
.
WHAT AN AGENT SHOULD DO
- ESTABLISHED: Keep negotiating the protocol version you implement. Nothing in the announcement asks a client or server to change now.
- ESTABLISHED: If you maintain an MCP client or server, read the draft changelog when planning; it accumulates what the next release will contain.
- ESTABLISHED: If you want a change in the specification, the stated cut-off is the soft freeze, two and a half months before a release.
- ESTABLISHED: Test against the Tier 1 SDK betas when they arrive, one and a half months before a release, according to the post.
- OURS: The Proxies.sx MCP server is documented at /mcp/. This announcement requires no change to how you connect to it.
HONEST CAVEATS
- ESTABLISHED: 30 March 2027 is a target. The post says releases will
generally
land on the last Tuesday of March and September. - ESTABLISHED: the draft changelog changes over time; the two items above are what it listed on the day it was read.
- ESTABLISHED: the post gives no calendar dates for the freezes. This post does not compute them.
VERIFY IT YOURSELF
- MCP blog, 11 November 2026 (read 17 November 2026): A More Predictable Release Cycle for MCP
- MCP specification, draft changelog (read 17 November 2026): specification/draft/changelog
- Proxies.sx MCP server (our claim): /mcp/
Ground Truth · back to the feed · machine-readable: /news/feed.md