Ext Ops Panel
Open dashboard
Comparison

E2B vs dominus-cli

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). dominus-cli is an MCP server published by rbxrootx. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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
MarketplaceE2Bdominus-cli
Docker MCP Catalog Listed
Version: sha256:ff4f9608cc4c
Forks (GitHub): 73
Pulls (Docker Hub): 23 873
Stars (Docker Hub): 2
Stars (GitHub): 393
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 3.4.0
Downloads/month (npm): 1 267
Downloads/week (npm): 411
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 dominus-cli
FactE2Bdominus-cli
Marketplaces that list it11
Stars (GitHub) (differs)393No figure on GitHub
Pulls (Docker Hub) (differs)23 873No figure on Docker Hub
Forks (GitHub) (differs)73No figure on GitHub
Last release (differs)Not published2026-10-26
Where it runs (differs)On your machine (mcp/e2b)On your machine (dominus-cli)
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0SEE LICENSE IN LICENSE
Repository (differs)github.com/e2b-dev/mcp-servergithub.com/rbxrootx/dominus
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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).

dominus-cli

In its own words, on npm registry (MCP servers):

romcp: a Roblox Studio MCP server and CLI for building, testing, profiling, and managing experiences.

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)

dominus-cli

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of dominus-cli publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of dominus-cli publish no settings it asks for, so we do not compare settings.

What it can do: E2B · What it can do: dominus-cli · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). 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