Ext Ops Panel
Open dashboard
Comparison

E2B vs oma

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). oma is a plugin bundle for AI coding tools published by First Fluke. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. 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
MarketplaceE2Boma
Docker MCP Catalog Listed
Version: sha256:ff4f9608cc4c
Forks (GitHub): 72
Pulls (Docker Hub): 23 520
Stars (Docker Hub): 2
Stars (GitHub): 392
Not marked · First seen
Not listed
Community marketplace first-fluke/oh-my-agent Not listed Listed
Version: 20.13.0
Forks (GitHub): 150
Stars (GitHub): 1 354
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 oma
FactE2Boma
Marketplaces that list it11
Stars (GitHub) (differs)392 (worse)1 354 (better)
Pulls (Docker Hub) (differs)23 520No figure on Docker Hub
Forks (GitHub) (differs)72 (worse)150 (better)
Last release (differs)Not published2026-10-24
Where it runs (differs)On your machine (mcp/e2b)Remote server (mcp.context7.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
Hooks it runs (differs)Not published6
Parts of the bundle (differs)Not a bundle52
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/e2b-dev/mcp-servergithub.com/first-fluke/oh-my-agent
Changes in the last 7 days (differs)07
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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

oma

In its own words, on Community GitHub marketplaces:

Portable multi-agent harness for .agents-based skills and workflows

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)

oma As a Claude Code plugin

Claude Code
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

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

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

Tools each declares

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

Settings each asks for

Only E2B asks for

  • E2B_API_KEY (secret)

Only oma asks for

  • SERENA_LOG_LEVEL

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

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