The MCP spec migration wave: why contract drift is about to spike

The MCP specification's 2026 release candidate is the largest revision since the protocol launched, a stateless core, extensions, and task primitives. Good for the ecosystem, and a rolling wave of exactly the change class that breaks consumers: server maintainers touching every tool definition as they migrate.

What migrations historically break

Watching public servers, the pattern in any migration window is consistent: 'consistency' renames (snake_case to camelCase and back), previously-loose fields gaining enums, required fields appearing as validation tightens, and wholesale description rewrites as maintainers modernize docs. None of it ships with deprecation windows, because the MCP ecosystem hasn't developed changelog culture yet, most servers have no changelog at all.

How to ride the wave instead of getting hit

Pin every remote dependency's contract now, before its maintainer migrates. Turn on nightly checks so drift surfaces within a day even without a deploy. Subscribe to the advisory feed for the servers you depend on, when a maintainer migrates, every consumer learns simultaneously instead of one incident at a time. And if you maintain a server: publish your changelog (we'll host it free) and give consumers a deprecation window; the badge tells them you do.