E2B vs telegram
E2B is an MCP server published by e2b-dev. Marketplaces we read that list it: 1 (Docker MCP Catalog). telegram is a plugin bundle for AI coding tools published by mjavadalavi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-20. 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 |  telegram |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ff4f9608cc4c Forks (GitHub): 72 Pulls (Docker Hub): 23 321 Stars (Docker Hub): 2 Stars (GitHub): 392 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: not stated Forks (GitHub): 0 Stars (GitHub): 0 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 | telegram |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 392 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 23 321 | 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 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/e2b-dev/mcp-server | github.com/mjavadalavi/claude-plugins-official |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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).
telegram
Connect a Telegram bot to your Claude Code session over MCP. The server logs in as a bot, forwards inbound messages into the session as <channel> notifications, and exposes tools to reply (with attachments up to 50MB), react with emoji, edit prior messages, and download inbound files. Built-in access control supports DM pairing flows and group/supergroup allowlists managed through the /telegram:access skill. Forum-topic routing via TELEGRAM_TOPIC_IDS lets a single bot fan out to multiple parallel Claude Code sessions, each bound to its own supergroup topic, so four sessions can work on four projects without racing for inbound messages. Proxy-aware transport (TELEGRAM_PROXY / HTTPS_PROXY) routes both text and multipart uploads through an HTTP proxy for use in regions where api.telegram.org is blocked or rate-limited.
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)
telegram As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install telegram@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of telegram publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of telegram publish no settings it asks for, so we do not compare settings.
What it can do: E2B · What it can do: telegram · 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.