E2B vs Arm MCP Server
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-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
| Marketplace |  E2B |  Arm MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 72 Pulls (Docker Hub): 23 219 Stars (Docker Hub): 2 Stars (GitHub): 393 Not marked · First seen |
Listed Version: sha256:ea7c4d1daeb9 Forks (GitHub): 20 Stars (GitHub): 91 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 2.4.0 Forks (GitHub): 20 Stars (GitHub): 91 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 | E2B | Arm MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 393 (better) | 91 (worse) |
| Pulls (Docker Hub) (differs) | 23 219 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 72 (better) | 20 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/e2b) | On your machine (docker.io/armlimited/arm-mcp:2.4.0) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | 7 |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/arm/mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
E2B
Giving Claude ability to run code with E2B via MCP (Model Context Protocol).
Arm MCP Server
Official Arm MCP server for code migration, optimization, and Arm architecture guidance
How to run each
E2B As a local MCP server: Docker image
claude mcp add --env "E2B_API_KEY=<YOUR_E2B_API_KEY>" --transport stdio e2b -- docker run -i --rm -e E2B_API_KEY mcp/e2bRequires: E2B_API_KEY (secret)
Arm 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.
Tools each declares
Only E2B declares
run_code
Only Arm MCP Server declares
apx_recipe_runcheck_imageknowledge_base_searchmcamigrate_ease_scanskopeosysreport_instructions
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Arm MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: E2B · What it can do: Arm MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.