A package rename looks exactly like a package that doesn't exist. My tool got it wrong, my fix got it wrong in the other direction, and the lesson generalises further than MCP. Plus the migration procedure I ship as an agent skill — and how to run it without one.
If you are migrating an MCP server right now, here is the thing that will cost you
an afternoon, before anything else in this post:
@modelcontextprotocol/sdk has no 2.x. It never will.
It stops at 1.30.0. If you go looking for @modelcontextprotocol/sdk@^2 you
will find nothing and conclude that v2 has not shipped yet. It has — on
The 2026-07-28 MCP spec makes tool catalogs cheap to scale — and tool selection your new bottleneck. Why agent reliability is now…
I ran a skill migration and nothing broke. Or so I thought. Break 3 in my migration diary noted that...
A remote MCP server can change its tool list or a tool's input schema without ever failing a health check. What counts as drift,…
If you've added an MCP server to a claude_desktop_config.json or an mcp.json file this year by...
TL;DR I introduced a SKILL layer while improving fare extraction in a MCP-based transit agent. After...
On July 28, the Model Context Protocol project shipped a new spec revision, 2026-07-28. I run backend...
