Zen vs telegram-per-project
Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). telegram-per-project is a plugin bundle for AI coding tools published by trezero. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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 |  Zen | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:02cbe1d325db Forks (GitHub): 1 035 Pulls (Docker Hub): 34 868 Stars (Docker Hub): 0 Stars (GitHub): 11 775 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 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 | Zen | telegram-per-project |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 775 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 34 868 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 035 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/zen) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 18 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 4 | 1, secrets among them: 0 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/beehiveinnovations/zen-mcp-server | github.com/trezero/telegram-per-project |
| 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
Zen
Bridges multiple AI models and CLIs, enabling orchestrated workflows across Claude Code, Gemini CLI, Codex CLI, and other AI development tools.
telegram-per-project
Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach Terminal 1 and messages to @beta_bot reach Terminal 2, with no cross-talk. Key features: - Per-project bot tokens via TELEGRAM_PROJECT_ID environment variable - Independent access policies per project, bootstrapped from global config - Response timeout — notifies senders when the assistant isn't responding (configurable, default 45s) - Full access control: DM pairing, allowlists, group mention detection - Reply, react, and edit_message tools for the assistant - Photo support with inline preview - Fully backward compatible — works as a single global bot if no project ID is set
How to run each
Zen As a local MCP server: Docker image
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "XAI_API_KEY=<YOUR_XAI_API_KEY>" --transport stdio zen -- docker run -i --rm -e GEMINI_API_KEY -e OPENAI_API_KEY -e OPENROUTER_API_KEY -e XAI_API_KEY mcp/zenRequires: GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), XAI_API_KEY (secret)
telegram-per-project
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of telegram-per-project publish no list of tools, so we do not compare tools.
Settings each asks for
Only Zen asks for
GEMINI_API_KEY (secret)OPENAI_API_KEY (secret)OPENROUTER_API_KEY (secret)XAI_API_KEY (secret)
Only telegram-per-project asks for
NODE_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Zen · What it can do: telegram-per-project · 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.