Ext Ops Panel
Open dashboard
Comparison

E2B vs Vibecode

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vibecode is an MCP server published by vibecodeapp.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceE2BVibecode
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
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 1
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 Vibecode
FactE2BVibecode
Marketplaces that list it11
Stars (GitHub) (differs)393 (better)1 (worse)
Pulls (Docker Hub) (differs)23 873No figure on Docker Hub
Forks (GitHub) (differs)73 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/e2b)Remote server (api.vibecodeapp.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/e2b-dev/mcp-servergithub.com/vibecode/vibecode
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-02
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 405

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

Vibecode

In its own words, on Official MCP Registry:

Build native iPhone apps and web apps by chatting. Vibecode's agent writes, builds and tests them.

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)

Vibecode As a remote MCP server

Claude Code
claude mcp add --transport http vibecode https://api.vibecodeapp.com/mcp

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

Only Vibecode has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

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

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