Ext Ops Panel
Open dashboard
Comparison

Zen vs han-core

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). han-core is a plugin bundle for AI coding tools published by testdouble. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. 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
MarketplaceZenhan-core
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 036
Pulls (Docker Hub): 35 661
Stars (Docker Hub): 0
Stars (GitHub): 11 834
Not marked · First seen
Not listed
Community marketplace testdouble/han Not listed Listed
Version: 3.2.0
Forks (GitHub): 28
Stars (GitHub): 342
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 han-core
FactZenhan-core
Marketplaces that list it11
Stars (GitHub) (differs)11 834 (better)342 (worse)
Pulls (Docker Hub) (differs)35 661No figure on Docker Hub
Forks (GitHub) (differs)1 036 (better)28 (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: 4Not published
Parts of the bundle (differs)Not a bundle24
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/testdouble/han
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-08

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.

han-core

In its own words, on Community GitHub marketplaces:

The shared foundation of the Han suite: the specialist agent roster the other plugins dispatch, the project-discovery skill with its project-scanner agent, and the canonical evidence and YAGNI rule files. The documentation skills live in han-documentation, the pre-planning research skills in han-research, the planning skills in han-planning, and the coding skills in han-coding; each depends on han-core.

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)

han-core As a Claude Code plugin

Claude Code
/plugin marketplace add testdouble/han
/plugin install han-core@han

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

Tools each declares

The marketplaces of han-core publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of han-core publish no settings it asks for, so we do not compare settings.

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

Where the data comes from: how the catalog is built