E2B vs io.github.buildkite/buildkite-mcp-server
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.buildkite/buildkite-mcp-server is an MCP server published by buildkite. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-17. 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 |  io.github.buildkite/buildkite-mcp-server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 72 Pulls (Docker Hub): 23 260 Stars (Docker Hub): 2 Stars (GitHub): 393 Not marked · First seen |
Listed Version: sha256:00e13d1742a5 Forks (GitHub): 39 Pulls (Docker Hub): 13 223 Stars (Docker Hub): 0 Stars (GitHub): 54 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Forks (GitHub): 39 Stars (GitHub): 54 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 | io.github.buildkite/buildkite-mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 393 (better) | 54 (worse) |
| Pulls (Docker Hub) (differs) | 23 260 (better) | 13 223 (worse) |
| Forks (GitHub) (differs) | 72 (better) | 39 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/e2b) | On your machine (ghcr.io/buildkite/buildkite-mcp-server:0.7.0) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | 24 |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/buildkite/buildkite-mcp-server |
| 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).
io.github.buildkite/buildkite-mcp-server
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.
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)
io.github.buildkite/buildkite-mcp-server As a local MCP server: Docker image
claude mcp add --env "BUILDKITE_API_TOKEN=<YOUR_BUILDKITE_API_TOKEN>" --transport stdio buildkite-mcp-server -- docker run -i --rm -e BUILDKITE_API_TOKEN run BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0 ghcr.io/buildkite/buildkite-mcp-server:0.7.0Requires: BUILDKITE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only E2B declares
run_code
Only io.github.buildkite/buildkite-mcp-server declares
access_tokencreate_buildcreate_pipelinecurrent_userget_artifactget_buildget_build_test_engine_runsget_clusterget_cluster_queueget_failed_executionsget_job_logsget_jobs
Show the remaining 12
get_pipelineget_testget_test_runlist_annotationslist_artifactslist_buildslist_cluster_queueslist_clusterslist_pipelineslist_test_runsupdate_pipelineuser_token_organization
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
Only E2B asks for
E2B_API_KEY (secret)
Only io.github.buildkite/buildkite-mcp-server asks for
BUILDKITE_API_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: E2B · What it can do: io.github.buildkite/buildkite-mcp-server · 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.