Ext Ops Panel
Open dashboard
Comparison

E2B vs cc-fleet

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). cc-fleet is a plugin bundle for AI coding tools published by Ethan Guo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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
MarketplaceE2Bcc-fleet
Docker MCP Catalog Listed
Version: sha256:ff4f9608cc4c
Forks (GitHub): 72
Pulls (Docker Hub): 23 304
Stars (Docker Hub): 2
Stars (GitHub): 392
Not marked · First seen
Not listed
Community marketplace ethanhq/cc-fleet Not listed Listed
Version: 0.4.2
Forks (GitHub): 30
Stars (GitHub): 160
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 cc-fleet
FactE2Bcc-fleet
Marketplaces that list it11
Stars (GitHub) (differs)392 (better)160 (worse)
Pulls (Docker Hub) (differs)23 304No figure on Docker Hub
Forks (GitHub) (differs)72 (better)30 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/e2b)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle5
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/e2b-dev/mcp-servergithub.com/ethanhq/cc-fleet
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18

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

cc-fleet

In its own words, on Community GitHub marketplaces:

Run any third-party LLM provider with an Anthropic-compatible API as real Claude Code agent-team teammates (terminal claude inside tmux or iTerm2) or one-shot subagents via the cc-fleet CLI — driven just like native teammates; your main session's own auth (OAuth or API key) is untouched, provider workers bill the provider key.

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)

cc-fleet As a Claude Code plugin

Claude Code
/plugin marketplace add ethanhq/cc-fleet
/plugin install cc-fleet@ethanhq

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

Tools each declares

The marketplaces of cc-fleet publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: E2B · What it can do: cc-fleet · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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