Ext Ops Panel
Open dashboard
Comparison

Zen vs neko-harness-doctor

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). neko-harness-doctor is a plugin bundle for AI coding tools published by aliksir. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-18. 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
MarketplaceZenneko-harness-doctor
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 035
Pulls (Docker Hub): 34 905
Stars (Docker Hub): 0
Stars (GitHub): 11 786
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.3
Forks (GitHub): 0
Stars (GitHub): 1
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 neko-harness-doctor
FactZenneko-harness-doctor
Marketplaces that list it11
Stars (GitHub) (differs)11 786 (better)1 (worse)
Pulls (Docker Hub) (differs)34 905No figure on Docker Hub
Forks (GitHub) (differs)1 035 (better)0 (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 bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/aliksir/neko-harness-doctor
Changes in the last 7 days00
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.

neko-harness-doctor

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

Diagnose your Claude Code harness (CLAUDE.md, settings.json, .mcp.json, hooks, skills, memory, MCP servers, and workflow) against 25 anti-pattern indicators. Outputs an S–E overall grade, per-category scores, violations with evidence citations, and prioritized Quick Wins. Includes an interactive fix flow: `--fix-mode propose` emits structured JSON proposals that Claude Code applies via the Edit tool with per-item user approval. Deterministic (no LLM — grep/AST/JSON only), zero runtime dependencies, bilingual (Japanese default, English via `--lang en`). When installed as a plugin, the bundled skill auto-triggers on natural-language requests like "diagnose my harness" and exposes `/neko-harness-doctor` as a slash command.

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)

neko-harness-doctor As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install neko-harness-doctor@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 neko-harness-doctor publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of neko-harness-doctor publish no settings it asks for, so we do not compare settings.

What it can do: Zen · What it can do: neko-harness-doctor · 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. 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