Dependency Migration MCP vs Voyager

In-depth architectural comparison of the Dependency Migration MCP and Voyager MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Dependency Migration MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Dependency Migration MCP Details

Choose Voyager when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Voyager Details

Feature & Specification Comparison

Specification	Dependency Migration MCP Developer Tools	Voyager Developer Tools
Summary	Through-the-upgrade dependency-migration briefs for LLM coding agents.	Cited, OSV-gated, injection-safe web briefs for coding agents. Verified, never raw web.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "dependency-migration-mcp": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

{
  "mcpServers": {
    "voyager": {
      "command": "npx",
      "args": [
        "-y",
        "@dir-ai/voyager"
      ]
    }
  }
}

Related MCP Server Comparisons