Ext Ops Panel
Open dashboard
Comparison

E2B vs Connections

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). Connections is an MCP server published by Lunarwerx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceE2BConnections
Docker MCP Catalog Listed
Version: sha256:ff4f9608cc4c
Forks (GitHub): 72
Pulls (Docker Hub): 23 321
Stars (Docker Hub): 2
Stars (GitHub): 392
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.253.0
Downloads/month (npm): 1 260
Downloads/week (npm): 392
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

E2B vs Connections
FactE2BConnections
Marketplaces that list it11
Stars (GitHub) (differs)392No figure on GitHub
Pulls (Docker Hub) (differs)23 321No figure on Docker Hub
Forks (GitHub) (differs)72No figure on GitHub
Last release (differs)Not published2026-10-18
Where it runs (differs)On your machine (mcp/e2b)On your machine (connections-mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/e2b-dev/mcp-serverNot stated
Changes in the last 7 days (differs)01
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

E2B

In its own words, on Docker MCP Catalog:

Giving Claude ability to run code with E2B via MCP (Model Context Protocol).

Connections

In its own words, on Official MCP Registry:

AWS, GitHub and connected services from your agent, no keys to paste, plus local shell and browser.

How to run each

E2B As a local MCP server: Docker image

Claude Code
claude mcp add --env "E2B_API_KEY=<YOUR_E2B_API_KEY>" --transport stdio e2b -- docker run -i --rm -e E2B_API_KEY mcp/e2b

Requires: E2B_API_KEY (secret)

Connections As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio connections -- npx -y connections-mcp

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

Tools each declares

The marketplaces of Connections publish no list of tools, so we do not compare tools.

Settings each asks for

Only E2B asks for

  • E2B_API_KEY (secret)

Only Connections asks for

  • CONNECTIONS_WORKSPACE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: E2B · What it can do: Connections · 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.

Where the data comes from: how the catalog is built