Ext Ops Panel
Open dashboard
Comparison

Arm MCP Server vs mcp-debugger

Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). mcp-debugger is an MCP server published by debugmcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceArm MCP Servermcp-debugger
Official MCP Registry Listed
Version: 2.4.0
Forks (GitHub): 20
Stars (GitHub): 93
Not marked · First seen
Listed
Version: 0.25.1
Downloads/month (npm): 7 482
Downloads/week (npm): 2 142
Forks (GitHub): 24
Stars (GitHub): 176
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:ea7c4d1daeb9
Forks (GitHub): 20
Stars (GitHub): 93
Not marked · First seen
Not listed

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

Arm MCP Server vs mcp-debugger
FactArm MCP Servermcp-debugger
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)93 (worse)176 (better)
Forks (GitHub) (differs)20 (worse)24 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (docker.io/armlimited/arm-mcp:2.4.0)On your machine (@debugmcp/mcp-debugger)
Transportstdiostdio
Tools it declares (differs)7Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/arm/mcpgithub.com/debugmcp/mcp-debugger
Changes in the last 7 days00
First seen2026-10-112026-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

Arm MCP Server

In its own words, on Official MCP Registry:

Official Arm MCP server for code migration, optimization, and Arm architecture guidance

mcp-debugger

In its own words, on Official MCP Registry:

Step-through debugging for AI agents: breakpoints, stepping and live variables in nine languages

How to run each

Arm MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio arm-mcp -- docker run -i --rm run --rm -i -v "<YOUR_WORKSPACE_PATH>:/workspace" -v "<YOUR_SSH_PRIVATE_KEY_PATH>:/run/keys/ssh-key.pem:ro" -v "<YOUR_SSH_KNOWN_HOSTS_PATH>:/run/keys/known_hosts:ro" docker.io/armlimited/arm-mcp:2.4.0

mcp-debugger As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-debugger -- npx -y @debugmcp/mcp-debugger stdio

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of mcp-debugger publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Arm MCP Server · What it can do: mcp-debugger · Compare two other plugins

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