Comparison

Zen vs obaass

obaass is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). obaass is a plugin bundle for AI coding tools published by cameronsjo. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-18. 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

Where each is published
Marketplace	Zen	obaass
Docker MCP Catalog	Listed Version: sha256:02cbe1d325db Forks (GitHub): 1 034 Pulls (Docker Hub): 34 915 Stars (Docker Hub): 0 Stars (GitHub): 11 786 Not marked · First seen 2026-10-11	Not listed
Community marketplace cameronsjo/obaass	Not listed	Removed on 2026-10-18 Version: not stated Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen 2026-10-14

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 obaass
Fact	Zen	obaassno longer listed · 2026-10-18
Marketplaces that list it (differs)	1	0
Stars (GitHub) (differs)	11 786	3
Pulls (Docker Hub) (differs)	34 915	No figure on Docker Hub
Forks (GitHub) (differs)	1 034	0
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
Licence (differs)	NOASSERTION	Not stated
Repository (differs)	github.com/beehiveinnovations/zen-mcp-server	github.com/cameronsjo/obaass
Changes in the last 7 days (differs)	0	4
First seen (differs)	2026-10-11	2026-10-14

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 obaass

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

Obsidian Turbocharged

Governed Obsidian vault access: hybrid retrieval, Markdown-native memory, HITL confirmations.

by The-40-Thieves · MCP server

Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job
Obsidian CLI MCP

Local MCP server for Obsidian Desktop via the official Obsidian CLI.

by dariuscorvus · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
gosidian

Self-hosted Obsidian-compatible markdown vault with a web UI and a 63-tool MCP server for AI agents

by daniele-chiappa · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
defang

Deploy any Docker Compose app to your own cloud account on AWS or GCP in minutes. The `/defang:deploy` skill guides you through the full workflow. Your code and secrets never…

by DefangLabs · Plugin bundle

Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job
HomeShed

Every tool your AI needs in one self-hosted install: memory, reasoning, git, Docker and more.

by keefng8 · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
obsidian-knowledge

Self-evolving Claude Code plugin that manages an Obsidian knowledge vault: capture, organize, index, garden — plus a meta-skill that improves the harness itself.

by crypdick · Plugin bundle

Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

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.

obaass

In its own words, on Community GitHub marketplaces:

Headless Obsidian orchestrator via Docker Compose

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)

obaass

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 obaass publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Zen · What it can do: obaass · 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 2026-10-18. We publish no contact details for plugin publishers.