Ext Ops Panel
Open dashboard
Comparison

Zen vs ds

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). ds is a plugin bundle for AI coding tools published by Andika Rachman. 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

Where each is published
MarketplaceZends
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 036
Pulls (Docker Hub): 34 879
Stars (Docker Hub): 0
Stars (GitHub): 11 784
Not marked · First seen
Not listed
Community marketplace andikarachman/data-science-plugin Not listed Listed
Version: 2.6.0
Forks (GitHub): 2
Stars (GitHub): 14
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 ds
FactZends
Marketplaces that list it11
Stars (GitHub) (differs)11 784 (better)14 (worse)
Pulls (Docker Hub) (differs)34 879No figure on Docker Hub
Forks (GitHub) (differs)1 036 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/zen)Remote server (mcp.context7.com/mcp)
Transport (differs)stdioStreamable HTTP
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 bundle28
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/andikarachman/data-science-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)no remote endpoint we checkResponded 18 h ago

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.

ds

In its own words, on Community GitHub marketplaces:

Data science and ML workflow tools. 9 agents, 8 commands, 19 skills, 9 templates for problem framing, preprocessing, validation, EDA, experimentation, review, deployment, and knowledge compounding.

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)

ds As a Claude Code plugin

Claude Code
/plugin marketplace add andikarachman/data-science-plugin
/plugin install ds@data-science-plugin

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

Only ds has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of ds publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Zen · What it can do: ds · 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