Legacy-Code-Migrator vs SonarQube MCP Server
Legacy-Code-Migrator is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). SonarQube MCP Server is an MCP server published by SonarSource. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  SonarQube MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.32.0 Forks (GitHub): 103 Stars (GitHub): 684 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 693 483 Stars (Docker Hub): 23 Stars (GitHub): 684 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Legacy-Code-Migrator | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 684 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 693 483 |
| Forks (GitHub) (differs) | No figure on GitHub | 103 |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | Remote server (legacy-migrator-mcp.vercel.app/api/mcp) | On your machine (docker.io/sonarsource/sonarqube-mcp) |
| Transport (differs) | SSE | stdio |
| Tools it declares (differs) | Not published | 25 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 3 |
| Licence (differs) | Not stated | NOASSERTION |
| Repository (differs) | Not stated | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (9 h ago) | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Legacy-Code-Migrator
Automated code modernizer converting legacy logic to ESNext.
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
Legacy-Code-Migrator As a remote MCP server
claude mcp add --transport sse legacy-migrator https://legacy-migrator-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
SonarQube MCP Server As a local MCP server: Docker image
claude mcp add --env "SONARQUBE_ORG=<YOUR_SONARQUBE_ORG>" --env "SONARQUBE_TOKEN=<YOUR_SONARQUBE_TOKEN>" --env "SONARQUBE_URL=<YOUR_SONARQUBE_URL>" --transport stdio sonarqube-mcp-server -- docker run -i --rm -e SONARQUBE_ORG -e SONARQUBE_TOKEN -e SONARQUBE_URL docker.io/sonarsource/sonarqube-mcpRequires: SONARQUBE_ORG (secret), SONARQUBE_TOKEN (secret), SONARQUBE_URL (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Legacy-Code-Migrator has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Legacy-Code-Migrator publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Legacy-Code-Migrator publish no settings it asks for, so we do not compare settings.
What it can do: Legacy-Code-Migrator · What it can do: SonarQube MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.