Ext Ops Panel
Open dashboard
Comparison

Zen vs great-cto

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). great-cto is a plugin bundle for AI coding tools published by avelikiy. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplaceZengreat-cto
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 036
Pulls (Docker Hub): 34 874
Stars (Docker Hub): 0
Stars (GitHub): 11 778
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 2.95.0
Forks (GitHub): 13
Stars (GitHub): 103
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

Zen vs great-cto
FactZengreat-cto
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)11 778 (better)103 (worse)
Pulls (Docker Hub) (differs)34 874No figure on Docker Hub
Forks (GitHub) (differs)1 036 (better)13 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/zen)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)18Not published
Environment variables it asks for (differs)4, secrets among them: 44, secrets among them: 2
Hooks it runs (differs)Not published44
Parts of the bundle (differs)Not a bundle159
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/avelikiy/great_cto
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.

What each says it does

Zen

In its own words, on Docker MCP Catalog:

Bridges multiple AI models and CLIs, enabling orchestrated workflows across Claude Code, Gemini CLI, Codex CLI, and other AI development tools.

great-cto

In its own words, on Claude Code: claude-plugins-community:

Full SDLC pipeline with 7 agents: architecture, code review, QA, security. Two decisions per feature, the rest is automated.

How to run each

Zen As a local MCP server: Docker image

Claude Code
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/zen

Requires: GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), XAI_API_KEY (secret)

great-cto As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install great-cto@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of great-cto 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)
  • XAI_API_KEY (secret)

Only great-cto asks for

  • GREAT_CTO_ROUTER_MAX_TOKENS (secret)
  • GREAT_CTO_ROUTER_MODEL
  • GREAT_CTO_ROUTER_TIMEOUT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Zen · What it can do: great-cto · 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. 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