Zen vs fleet
fleet is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
Zen is an MCP server published by BeehiveInnovations. Marketplaces we read that list it: 1 (Docker MCP Catalog). fleet is a plugin bundle for AI coding tools published by the operator. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. 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 034 Pulls (Docker Hub): 34 956 Stars (Docker Hub): 0 Stars (GitHub): 11 786 Not marked · First seen |
Not listed |
| Community marketplace expardus/fleet | Not listed | Removed on 2026-10-19 Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 4 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 | fleetno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 11 786 | 4 |
| Pulls (Docker Hub) (differs) | 34 956 | 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 |
| Parts of the bundle (differs) | Not a bundle | 17 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/beehiveinnovations/zen-mcp-server | github.com/expardus/fleet |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
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 fleet
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
A la carte toolkit for Claude Code. Best practices, persistent memory, and agent-team planning — pick what fits your project.
-
Control and coordinate multiple Claude Code sessions via cyberian's agentapi wrapper
-
Run any third-party LLM provider with an Anthropic-compatible API as real Claude Code agent-team teammates (terminal claude inside tmux or iTerm2) or one-shot subagents via the…
-
Complete toolkit for building and distributing Claude Code plugins, skills, hooks, subagents, slash commands, marketplaces, and MCP servers
-
Research-backed orchestration for Claude Code. Structured workflow from idea to production with parallel execution, session memory, 70-point validation, autonomous mode, and…
-
MCP server that orchestrates multiple Claude CLI instances as parallel workers with a real-time dashboard
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.
fleet
Three-tier command for Claude Code sessions: an interface tier that owns the plan, a supervisor tier that dispatches and gates, and worker sessions that survive reboots.
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)
fleet
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 fleet publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of fleet publish no settings it asks for, so we do not compare settings.
What it can do: Zen · What it can do: fleet · 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.