zephyr-scale-mcp-server vs SonarQube MCP Server
zephyr-scale-mcp-server is an MCP server published by Milo0821. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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-08. 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 |  zephyr-scale-mcp-server |  SonarQube MCP Server |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.10.0 Downloads/month (npm): 548 Downloads/week (npm): 280 Forks (GitHub): 6 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.31.0 Forks (GitHub): 103 Stars (GitHub): 680 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 678 282 Stars (Docker Hub): 23 Stars (GitHub): 680 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 | zephyr-scale-mcp-server | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 7 (worse) | 680 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 678 282 |
| Forks (GitHub) (differs) | 6 (worse) | 103 (better) |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | On your machine (zephyr-scale-mcp-server) | On your machine (docker.io/sonarsource/sonarqube-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 25 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 3 |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/milo0821/zephyr_mcp_server | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
zephyr-scale-mcp-server
Model Context Protocol (MCP) server for Zephyr Scale test case management with comprehensive STEP_BY_STEP, PLAIN_TEXT, and BDD support
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
zephyr-scale-mcp-server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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.
Tools each declares
The marketplaces of zephyr-scale-mcp-server publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of zephyr-scale-mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: zephyr-scale-mcp-server · What it can do: SonarQube MCP Server · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.