Ext Ops Panel
Open dashboard
Comparison

autonomous-dev vs SonarQube MCP Server

autonomous-dev is a plugin bundle for AI coding tools published by Adiomas. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-15. 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

Where each is published
Marketplaceautonomous-devSonarQube MCP Server
Community marketplace adiomas/claude-code-adiomas-plugins Not seen in the last pass
Version: 4.2.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.21.0
Forks (GitHub): 103
Stars (GitHub): 664
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:925c88bc7cab
Forks (GitHub): 103
Pulls (Docker Hub): 1 517 308
Stars (Docker Hub): 23
Stars (GitHub): 664
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

autonomous-dev vs SonarQube MCP Server
Factautonomous-devSonarQube MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)664 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub1 517 308
Forks (GitHub) (differs)0 (worse)103 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@anthropic/mcp-sequential-thinking)On your machine (docker.io/sonarsource/sonarqube-mcp)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published25
Environment variables it asks for (differs)Not published3, secrets among them: 3
Hooks it runs (differs)10Not published
Parts of the bundle (differs)44Not a bundle
Licence (differs)MITNOASSERTION
Repository (differs)github.com/adiomas/claude-code-adiomas-pluginsgithub.com/sonarsource/sonarqube-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-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

autonomous-dev

In its own words, on Community GitHub marketplaces:

Zero-error autonomous development with pre-merge validation, mutation testing, and MCP integration

SonarQube MCP Server

In its own words, on Official MCP Registry:

Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.

How to run each

autonomous-dev As a Claude Code plugin

Claude Code
/plugin marketplace add adiomas/claude-code-adiomas-plugins
/plugin install autonomous-dev@adiomas-plugins

SonarQube MCP Server As a local MCP server: Docker image

Claude Code
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 autonomous-dev publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of autonomous-dev publish no settings it asks for, so we do not compare settings.

What it can do: autonomous-dev · 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.

Where the data comes from: how the catalog is built