Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding

MCP now ships on a six-month clock

Written November 12, 2026

Maintainers no longer have to guess when the next MCP specification lands. SEP-3398 fixes releases to the last Tuesday of March and September, with Tier 1 SDK betas about six weeks ahead, so testing windows can go on a calendar.

The new calendar

SEP-3398, Release Cycle Updates, sets the Model Context Protocol's release rhythm in writing. Specification releases now occur every six months, generally on the last Tuesday of March and September. The SEP was created on September 17, 2026 and accepted on October 14, 2026, authored by Kurtis Van Gent on behalf of the Core Maintainers.

Each release runs on an eight-month cycle: two months of planning, a defined Core Maintainer review window, and stabilization before publication. Successive cycles overlap by two months, so planning for the next release starts while the current one is finishing. A proposal that is not ready moves to a later release. The date does not move to wait for it.

The next release, dated

The transition moves the release previously targeted for December 2026 to March 30, 2027 — the last Tuesday of March, with the version to be named 2027-03-30. The last specification release was July 28, 2026, and the first cycle under the new process uses planning completed in August 2026. Planning for the September 2027 release begins in late January 2027.

For a team maintaining an MCP server, the practical effect is simple: the current specification, 2026-07-28, is the one to build against through the winter, and the next breaking-change window has a date on it.

The milestones that matter to maintainers

Four dates inside each cycle do the work. The Core Maintainer review window opens six months before release and closes at soft freeze. Soft freeze falls two and a half months before release: by then, every proposal in the release must be Final and merged, with its specification text, schema changes and conformance tests in place. Tier 1 SDK betas land one and a half months before release — about six weeks — giving client and server developers a testing window before hard freeze. Hard freeze falls one month before release, after which only critical security fixes and release-blocking defects can be considered, and only by a full Core Maintainer vote.

If you maintain an SDK integration, the beta milestone is your cue. That is the point where the frozen scope is stable enough to test against, and beta release notes name the target specification release, the available functionality and the known gaps.

What the calendar does not change

SEP-3398 is a process change. It introduces no protocol messages, no schema changes and no version-negotiation changes, and it sets no new requirements for deployed clients and servers. Existing date-based specification versions remain valid. Nothing in your current MCP setup needs to change because this SEP exists.

The deprecation clock already running

The calendar sits on top of changes already in force. The 2026-07-28 specification removed the initialize handshake and protocol sessions, and deprecated Roots, Sampling and Logging under a feature lifecycle that keeps a deprecated feature working for at least twelve months before it becomes eligible for removal. Counted from July 2026, that window runs to about July 2027 — which lands between the March and September 2027 releases. The SEP phrases removal as eligibility inside a window, not a fixed date, and this page keeps it that way: plan the migration inside the window rather than betting on its last day.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: MCP reference servers 2.3.0: what's new · MCP's July spec killed sessions — tooling may not know · Patch your MCP reference servers now · MCP Gateway Registry 1.37 tightens wildcards