Zen vs pair-pipeline
pair-pipeline is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). pair-pipeline is a plugin bundle for AI coding tools published by Pair Pipeline Contributors. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:02cbe1d325db Forks (GitHub): 1 036 Pulls (Docker Hub): 34 963 Stars (Docker Hub): 0 Stars (GitHub): 11 792 Not marked · First seen |
Not listed |
| Community marketplace gantisstorm/claude-code-pair-planning-framework | Not listed | Removed on 2026-10-21 Version: 1.7.0 Forks (GitHub): 1 Stars (GitHub): 6 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 | pair-pipelineno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 11 792 | 6 |
| Pulls (Docker Hub) (differs) | 34 963 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 036 | 1 |
| 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 | Not published |
| Parts of the bundle (differs) | Not a bundle | 7 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/beehiveinnovations/zen-mcp-server | github.com/gantisstorm/claude-code-pair-planning-framework |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-19 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of pair-pipeline
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Multi-agent development workflows (planning, implementation, review, testing agents)
-
Multi-agent AI pipelines with structural write/review isolation, crash-safe state recovery, and spec-driven development. Run sequential, parallel fan-out, iterative-loop, or…
-
Architecture, executable planning, governed execution, and adversarial review for coding agents.
-
A multi-agent development framework that splits project builds into phases using three specialized roles: an Orchestrator (plans and coordinates), Workers (implement code), and…
-
Multi-agent orchestration for coding agents: run external agent CLIs (Codex, Claude Code, OpenCode, Grok Build, Gemini, Devin CLI) as independent reviewers, stateful repository…
-
Autonomous overnight coding agent. Queue tasks in YAML, run them via Claude CLI while you sleep, and use self-healing audit-fix loops to hit any quality target. Includes skills…
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.
pair-pipeline
Multi-agent orchestration for complex coding tasks without MCP. Scouts gather raw context, planner synthesizes structured narrative (task, architecture, context, relationships, implementation notes, ambiguities) into per-file instructions. Full discovery loop with user checkpoints and parallel execution.
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/zen
Requires: GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), XAI_API_KEY (secret)
pair-pipeline
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 pair-pipeline publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of pair-pipeline publish no settings it asks for, so we do not compare settings.
What it can do: Zen · What it can do: pair-pipeline · 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.