Zen vs commy
Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). commy is a plugin bundle for AI coding tools published by Code For Breakfast. Marketplaces we read that list it: 1 (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
| Marketplace |  Zen | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:02cbe1d325db Forks (GitHub): 1 036 Pulls (Docker Hub): 34 881 Stars (Docker Hub): 0 Stars (GitHub): 11 784 Not marked · First seen |
Not listed |
| Community marketplace codeforbreakfast/commy | Not listed | Listed Version: 0.25.4 Forks (GitHub): 0 Stars (GitHub): 2 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 | commy |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 784 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 34 881 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 036 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/zen) | On your machine (@codeforbreakfast/commy-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 18 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 4 | 6, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/beehiveinnovations/zen-mcp-server | github.com/codeforbreakfast/commy |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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.
commy
Hexagonal MCP plugin exposing commy ports to Claude Code sessions. V1 hard-wired to the Zulip driven adapter.
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)
commy As a Claude Code plugin
/plugin marketplace add codeforbreakfast/commy
/plugin install commy@commyCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of commy 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 commy asks for
COMMY_CATCHUP_WINDOW_SECONDS_USER_CONFIGCOMMY_SUBSCRIBE_USER_CONFIGZULIP_MINTER_API_KEY (secret)ZULIP_MINTER_EMAILZULIP_SITEnpm_config_min_release_age
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Zen · What it can do: commy · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.