Ext Ops Panel
Open dashboard
Comparison

E2B vs Desktop Commander

E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). Desktop Commander is an MCP server published by wonderwhy-er. Marketplaces we read that list it: 6 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-12. 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
MarketplaceE2BDesktop Commander
Docker MCP Catalog Listed
Version: sha256:ff4f9608cc4c
Forks (GitHub): 72
Pulls (Docker Hub): 23 197
Stars (Docker Hub): 2
Stars (GitHub): 393
Not marked · First seen
Listed
Version: sha256:5df787069e37
Pulls (Docker Hub): 235 008
Stars (Docker Hub): 22
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.2.52
No figure published
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 261
Stars (GitHub): 9 998
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 0.2.0
No figure published
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
No figure published
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 Desktop Commander
FactE2BDesktop Commander
Marketplaces that list it (differs)1 (worse)6 (better)
Stars (GitHub) (differs)393 (worse)9 998 (better)
Pulls (Docker Hub) (differs)23 197 (worse)235 008 (better)
Forks (GitHub) (differs)72 (worse)1 261 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/e2b)On your machine (@wonderwhy-er/desktop-commander)
Transportstdiostdio
Tools it declares (differs)126
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle7
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/e2b-dev/mcp-servergithub.com/wonderwhy-er/desktopcommandermcp
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.

Tools each declares

Only E2B declares

  • run_code

Only Desktop Commander declares

  • create_directory
  • edit_block
  • force_terminate
  • get_config
  • get_file_info
  • get_more_search_results
  • get_prompts
  • get_recent_tool_calls
  • get_usage_stats
  • give_feedback_to_desktop_commander
  • interact_with_process
  • kill_process
Show the remaining 14
  • list_directory
  • list_processes
  • list_searches
  • list_sessions
  • move_file
  • read_file
  • read_multiple_files
  • read_process_output
  • set_config_value
  • start_process
  • start_search
  • stop_search
  • write_file
  • write_pdf

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

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

What it can do: E2B · What it can do: Desktop Commander · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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