Semgrep vs SonarQube MCP Server
Semgrep is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-10-17. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Listed Version: sha256:925c88bc7cab Forks (GitHub): 105 Pulls (Docker Hub): 1 535 611 Stars (Docker Hub): 23 Stars (GitHub): 665 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.21.0 Forks (GitHub): 105 Stars (GitHub): 665 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 | Semgrep | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 665 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 535 611 |
| Forks (GitHub) (differs) | No figure on GitHub | 105 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.semgrep.ai/mcp) | On your machine (docker.io/sonarsource/sonarqube-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | 8 | 25 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 3 |
| Licence (differs) | Apache-2.0 | NOASSERTION |
| Repository (differs) | Not stated | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | 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
Semgrep
MCP server for using Semgrep to scan code for security vulnerabilities.
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
Semgrep As a remote MCP server
claude mcp add --transport http semgrep https://mcp.semgrep.ai/mcp
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-mcp
Requires: 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 Semgrep has a remote endpoint we check. How we check endpoints
Tools each declares
Only Semgrep declares
get_abstract_syntax_treeget_supported_languagessecurity_checksemgrep_findingssemgrep_rule_schemasemgrep_scansemgrep_scan_localsemgrep_scan_with_custom_rule
Only SonarQube MCP Server declares
analyze_code_snippetanalyze_file_listchange_sonar_issue_statuscreate_webhookget_component_measuresget_project_quality_gate_statusget_raw_sourceget_scm_infoget_system_healthget_system_infoget_system_logsget_system_status
Show the remaining 13
list_enterpriseslist_languageslist_portfolioslist_quality_gateslist_rule_repositorieslist_webhooksping_systemsearch_dependency_riskssearch_metricssearch_my_sonarqube_projectssearch_sonar_issues_in_projectsshow_ruletoggle_automatic_analysis
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Semgrep publish no settings it asks for, so we do not compare settings.
What it can do: Semgrep · What it can do: SonarQube MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.