E2B vs membase
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). membase is a plugin bundle for AI coding tools published by aristoapp. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 72 Pulls (Docker Hub): 23 208 Stars (Docker Hub): 2 Stars (GitHub): 393 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | membase |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 393 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 23 208 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 72 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/e2b) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 1, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 4 |
| Parts of the bundle (differs) | Not a bundle | 19 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/aristoapp/claude-membase |
| 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).
membase
Membase connects Claude Code to Membase Cloud, giving Claude persistent memory and wiki workflows across coding sessions. It can recall relevant prior context before prompts, save durable project decisions and user preferences, and search stable wiki documents while you work. The plugin includes slash commands, MCP tools, project-aware recall, optional summary capture, and privacy safeguards for avoiding secrets, raw source files, and private blocks.
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)
membase
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 membase publish no list of tools, so we do not compare tools.
Settings each asks for
Only E2B asks for
E2B_API_KEY (secret)
Only membase asks for
MEMBASE_CLAUDE_PLUGIN
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: E2B · What it can do: membase · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.