Capgo vs Arm MCP Server
Capgo is an MCP server published by capgo.app. Marketplaces we read that list it: 1 (Official MCP Registry). Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-17. 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 |  Capgo |  Arm MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 2.4.0 Forks (GitHub): 21 Stars (GitHub): 93 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:ea7c4d1daeb9 Forks (GitHub): 21 Stars (GitHub): 93 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 | Capgo | Arm MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 93 |
| Forks (GitHub) (differs) | No figure on GitHub | 21 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.capgo.app/mcp) | On your machine (docker.io/armlimited/arm-mcp:2.4.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 7 |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | Not stated | github.com/arm/mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | 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
Capgo
Ship and update Capacitor apps: live updates, channels, rollouts, devices, native builds, stats.
Arm MCP Server
Official Arm MCP server for code migration, optimization, and Arm architecture guidance
How to run each
Capgo As a remote MCP server
claude mcp add --transport http capgo https://api.capgo.app/mcpArm MCP Server As a local MCP server: Docker image
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.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Capgo has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Capgo 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: Capgo · What it can do: Arm MCP Server · 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.