Ext Ops Panel
Open dashboard
Comparison

E2B vs agent-smith

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). agent-smith is a plugin bundle for AI coding tools published by maxencemeloni. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceE2Bagent-smith
Docker MCP Catalog Listed
Version: sha256:ff4f9608cc4c
Forks (GitHub): 72
Pulls (Docker Hub): 23 229
Stars (Docker Hub): 2
Stars (GitHub): 393
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 2.5.1
Forks (GitHub): 0
Stars (GitHub): 7
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 agent-smith
FactE2Bagent-smith
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)393 (better)7 (worse)
Pulls (Docker Hub) (differs)23 229No figure on Docker Hub
Forks (GitHub) (differs)72 (better)0 (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
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/e2b-dev/mcp-servergithub.com/maxencemeloni/claude-code-agent-smith
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

In its own words, on Docker MCP Catalog:

Giving Claude ability to run code with E2B via MCP (Model Context Protocol).

agent-smith

In its own words, on Claude Code: claude-plugins-community:

Agent Smith adds two slash commands to Claude Code: /analyze-agent performs a full configuration audit across 7 evaluation pillars (Security, Instruction Clarity, Configuration Quality, Context Efficiency, Command Design, Hook Safety, MCP Integration), scores each area, identifies issues by severity, and walks you through an interactive fix workflow. /create-agent scaffolds a new configuration with security deny rules and best practices. The tool is honest about its scope — it only measures user-configurable components and clearly states what's outside its reach.

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)

agent-smith As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-smith@claude-community

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

Tools each declares

The marketplaces of agent-smith publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: E2B · What it can do: agent-smith · 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. 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