Ext Ops Panel
Open dashboard
Comparison

Zen vs io.github.las7/memharness

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.las7/memharness is an MCP server published by las7. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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
MarketplaceZenio.github.las7/memharness
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 034
Pulls (Docker Hub): 34 956
Stars (Docker Hub): 0
Stars (GitHub): 11 786
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 165
Downloads/week (npm): 31
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

Zen vs io.github.las7/memharness
FactZenio.github.las7/memharness
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)11 786 (better)6 (worse)
Pulls (Docker Hub) (differs)34 956No figure on Docker Hub
Forks (GitHub) (differs)1 034 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/zen)On your machine (@memharness/mcp)
Transportstdiostdio
Tools it declares (differs)18Not published
Environment variables it asks for (differs)4, secrets among them: 41, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle4
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/las7/memharness
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.

io.github.las7/memharness

In its own words, on Official MCP Registry:

Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file.

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)

io.github.las7/memharness As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio memharness -- npx -y @memharness/mcp

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

Tools each declares

The marketplaces of io.github.las7/memharness 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)
  • OPENROUTER_API_KEY (secret)
  • XAI_API_KEY (secret)

Only io.github.las7/memharness asks for

  • MEMHARNESS_DB

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

What it can do: Zen · What it can do: io.github.las7/memharness · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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