
Dependency Migration Mcp
io.github.SolvoHQPublished by GitHub account SolvoHQv0.1.2Updated Oct 24, 2026
Through-the-upgrade dependency-migration briefs for LLM coding agents.
Overview
A local MCP server that gives coding agents structured migration briefs for major-version dependency upgrades, covering breaking changes and stale-API pitfalls.
- What you can do
- Retrieve a migration brief for a package and version pair, with per-breaking-change category, before/after, fix and codemod coverage, plus warnings about outdated API knowledge the agent should suppress.
- When to use it
- Use it mid-upgrade, right after bumping a major version and seeing the build fail, so the agent gets a brief before editing. It covers only a few pairs: tailwindcss 3 to 4, next 14 to 15 and react 18 to 19.
- Requirements
- Runs locally over stdio as a Python package, launched with uvx or pip (Python 3.10+). No account, API key or environment variables; data is bundled and offline, so no runtime network calls.
Installation
In SourceWeft
- Open Dependency Migration Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
dependency-migration-mcp
Through-the-upgrade migration briefs for LLM coding agents.
Official codemods auto-apply the mechanical ~90% of a major version bump. This MCP server briefs your agent on the non-mechanical ~10% that still leaves the build red, and corrects the agent's stale-v3-training hallucination of the old API surface — the part a codemod cannot do.
For one (package, from, to) triple it returns a structured brief: per
breaking change — category, before/after, how to grep every occurrence in
your code, the fix, and whether the free codemod already covers it — plus a
top-level list of the specific old-API hallucinations the agent must suppress.
Supported matrix
Versions are normalised by major (3, 3.4.1, v3, ^3 → 3). An unknown
package or unsupported pair returns a clean structured not_found (with the
supported matrix) — never an exception. Data is hand-curated and offline (no
runtime network calls).
Install (one command, zero account)
That fetches, builds, and runs the stdio MCP server straight from public
GitHub. No clone, no signup, no API key. (Need uvx? pip install uv.)
Prefer pip? A venv fallback:
Wire it into your agent
Claude Code — claude mcp add:
or drop this into .mcp.json at your project root:
Cursor — ~/.cursor/mcp.json:
Tool
get_migration(package: str, from_version: str, to_version: str) -> dict
Read-only. Returns a JSON-able brief: summary (counts, codemod command +
what it does/doesn't cover, stale_training_hallucination_warnings,
positioning) and breaking_changes[] (each with id, title, category
∈ {mechanical, non-mechanical, behavioural, removed-api, config-shape},
what_changed.{description,before,after},
find_occurrences.{guidance,patterns}, fix, codemod_covered, and
codemod_command when covered).
Use it mid-upgrade: right after bumping a major version and seeing the build
go red, ask the agent to call get_migration before it starts editing.
Smoke test
Imports the server, calls get_migration("tailwindcss","3","4") and asserts
the @tailwind→@import change, the CSS-first config-shape change, and a
stale-training hallucination warning are present; then asserts an unknown
pair returns a clean not_found.
Source: README.md at commit 6cf6a9b
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.