Ext Ops Panel
Open dashboard
Comparison

Architect Playbook vs SonarQube MCP Server

Architect Playbook is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

Architect Playbook is a plugin bundle for AI coding tools published by Ben Sheridan-Edwards. 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-23. 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

Where each is published
MarketplaceArchitect PlaybookSonarQube MCP Server
Community marketplace bensheridanedwards/architectplaybook Removed on 2026-10-18
Version: not stated
Forks (GitHub): 5
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.30.0
Forks (GitHub): 104
Stars (GitHub): 670
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:925c88bc7cab
Forks (GitHub): 104
Pulls (Docker Hub): 1 577 825
Stars (Docker Hub): 23
Stars (GitHub): 670
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

Architect Playbook vs SonarQube MCP Server
FactArchitect Playbookno longer listed · SonarQube MCP Server
Marketplaces that list it (differs)02
Stars (GitHub) (differs)3670
Pulls (Docker Hub) (differs)No figure on Docker Hub1 577 825
Forks (GitHub) (differs)5104
Last release (differs)Not published2026-10-23
Where it runs (differs)Installs as a plugin bundleOn 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
Parts of the bundle (differs)20Not a bundle
Licence (differs)MITNOASSERTION
Repository (differs)github.com/bensheridanedwards/architectplaybookgithub.com/sonarsource/sonarqube-mcp-server
Changes in the last 7 days (differs)21
First seen (differs)2026-10-152026-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 Architect Playbook

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • ff-review

    Plugin description Code quality review plugin based on Frontend Fundamentals 4 principles (readability, predictability, cohesion, coupling). Supports React and Angular with…

    by rrkkee015 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • code-review-ai

    AI-powered architectural review and code quality analysis

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • code-review-ai

    AI-powered architectural review and code quality analysis

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • deep-review

    Comprehensive code review skill with 53 specialized agents for architecture, code quality, error handling, types, comments, tests, accessibility, localization, concurrency…

    by Iron-Ham · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • code-architecture-review

    Drop this plugin into any project and ask Claude to "review my architecture." It scans for clean architecture violations, SOLID breaches, code smells, and structural anti-patterns…

    by Farjmand · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • audit-project

    Multi-agent iterative code review until zero issues remain. Spawns up to 10 specialist reviewers (code quality, security, performance, test coverage, architecture, database, API…

    by agent-sh · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Architect Playbook

In its own words, on Community GitHub marketplaces:

Opinionated, evidence-verified audits of TypeScript and React codebases: architecture, testing, security, dependencies, quality gates, and more, with a Repository Quality Score.

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

Architect Playbook

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 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 Architect Playbook publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Architect Playbook publish no settings it asks for, so we do not compare settings.

What it can do: Architect Playbook · 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