recon vs SonarQube MCP Server
recon is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
recon is a plugin bundle for AI coding tools published by doruk. No marketplace we read lists it any more. 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-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace adcreative-ai/recon-plugin | Removed on 2026-10-15 Version: 0.23.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.21.0 Forks (GitHub): 104 Stars (GitHub): 669 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 104 Pulls (Docker Hub): 1 570 067 Stars (Docker Hub): 23 Stars (GitHub): 669 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 | reconno longer listed · | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 669 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 570 067 |
| Forks (GitHub) (differs) | 0 | 104 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | 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 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | Not stated | NOASSERTION |
| Repository (differs) | github.com/adcreative-ai/recon-plugin | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of recon
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Work on issues from GitHub, Linear, or GitLab
-
Teamwork Graph CLI is Atlassian's agent-first interface to your entire work context: Jira issues, Confluence pages, Bitbucket PRs, along with your connected third-party data…
-
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
-
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
-
Jira QA scope and business-friendly Jira reports built from tickets and commits
-
A collection of project-agnostic skills for common engineering tasks such as ticket refinement, planning, code reviews, agent memory hygiene, skill authoring, and more.
What each says it does
recon
Deterministic Jira task recon pipeline: blocker triage → code discovery → decree routing, with live visual evidence
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
recon
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-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.
Tools each declares
The marketplaces of recon publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of recon publish no settings it asks for, so we do not compare settings.
What it can do: recon · What it can do: SonarQube MCP Server · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.