MCP now ships on a clock. The next spec lands on 30 March 2027.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On 11 November 2026 the MCP lead maintainers set a six-month schedule: spec releases on the last Tuesday of March and September, starting with version 2027-03-30. Proposals must be Final and merged by a soft freeze two and a half months before release, and Tier 1 SDK betas arrive a month and a half before.
Why it matters
No more guessing when the next protocol version drops. A proposal that misses the freeze waits for the next release instead of delaying the spec, so the date holds. Version strings stay dates, and version negotiation does not change.
What to do
Put 30 March 2027 in your server's roadmap today, and plan to test against the Tier 1 SDK betas about six weeks before it.

My take
Lior Aharonov
Founder, 7IT Solutions
A spec with a calendar is a spec you can build a business on. Miss the train and you wait six months.
Sources
| MCP blog: MCP's release cycle | blog.modelcontextprotocol.io |
Researched with AI tools; every fact is checked against the linked sources.