al-development-collection-for-claude-code vs SonarQube MCP Server
al-development-collection-for-claude-code is a plugin bundle for AI coding tools published by javiarmesto. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-11. 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 |  al-development-collection-for-claude-code |  SonarQube MCP Server |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 4.2.0 Forks (GitHub): 37 Stars (GitHub): 115 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.32.0 Forks (GitHub): 103 Stars (GitHub): 684 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 696 758 Stars (Docker Hub): 23 Stars (GitHub): 684 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 | al-development-collection-for-claude-code | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 115 (worse) | 684 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 696 758 |
| Forks (GitHub) (differs) | 37 (worse) | 103 (better) |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | Remote server (mcp.context7.com/mcp) | On your machine (docker.io/sonarsource/sonarqube-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 25 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 3 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 41 | Not a bundle |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/javiarmesto/aldc-al-development-collection-for-github-copilot | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 47 h ago returned HTTP 405 | 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
al-development-collection-for-claude-code
ALDC (AL Development Collection) is a comprehensive AI-assisted development toolkit for Microsoft Dynamics 365 Business Central. It provides 4 specialized agents (architect, conductor, developer, presales), 11 domain knowledge skills (API, events, pages, performance, testing, etc.), and 6 development workflows (spec creation, build, PR preparation, etc.). Key features: • Extension-only development — never modifies base application objects • Human-in-the-Loop gates at critical decision points • TDD/spec-driven development cycle • Event-driven architecture patterns • Skills Evidencing — agents declare which skills and patterns they applied • 8 path-scoped AL rules (injected via /aldc:al-initialize) • 3 MCP servers for AL symbols, documentation, and Microsoft Learn First-time setup: run /aldc:al-initialize in your AL project directory.
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
al-development-collection-for-claude-code As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install al-development-collection-for-claude-code@claude-communitySonarQube 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.
Only al-development-collection-for-claude-code has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of al-development-collection-for-claude-code publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of al-development-collection-for-claude-code publish no settings it asks for, so we do not compare settings.
What it can do: al-development-collection-for-claude-code · What it can do: SonarQube MCP Server · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.