mcp-migrate

Adoption judgment: mcp-migrate is worth evaluating if you maintain an MCP Server and need to assess compatibility with the MCP 2026-07-28 specification revision. The available evidence is not strong enough to show that it is stable across many real-world projects, so it is better treated as a tool to try in a test branch than as the sole release gate.

In practical terms, the repository describes a tool for finding and fixing what the specification revision may break. It advertises 21 checks, 5 autofixers, and a readiness board. A more accurate comparison is a specification-migration assistant or a specialized linter for MCP Servers: it can help developers organize compatibility findings and attempt fixes where supported, while the readiness board can help track migration status. The evidence does not list the individual rules, fix boundaries, supported languages, or complete execution workflow, so the rule count should not be read as proof of complete coverage.

The main operational threshold is understanding MCP Server code and the differences between the current and target specification, followed by reviewing any generated changes.