clio-coder-dev vs Desktop Commander
clio-coder-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
clio-coder-dev is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Desktop Commander is an MCP server published by wonderwhy-er. Marketplaces we read that list it: 6 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. 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 |   Desktop Commander | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.4.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.5.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 966 995 Downloads/week (npm): 159 845 Forks (GitHub): 1 258 Stars (GitHub): 10 123 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 258 Stars (GitHub): 10 123 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:5df787069e37 Forks (GitHub): 1 258 Pulls (Docker Hub): 239 568 Stars (Docker Hub): 22 Stars (GitHub): 10 123 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 258 Stars (GitHub): 10 123 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 258 Stars (GitHub): 10 123 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 | clio-coder-devno longer listed · | Desktop Commander |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 6 |
| Stars (GitHub) (differs) | 8 | 10 123 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 239 568 |
| Forks (GitHub) (differs) | 5 | 1 258 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@wonderwhy-er/desktop-commander) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 26 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 7 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/wonderwhy-er/desktopcommandermcp |
| Changes in the last 7 days (differs) | 6 | 1 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
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 clio-coder-dev
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Six focused slash commands for safer, more deliberate coding sessions. Save and restore named git checkpoints, review diffs before committing, analyze blast radius before changing…
-
Delegate coding tasks from Codex to local Claude Code; preserves trusted Claude runtime customizations by default and supports SESSION_ID resume plus mcp/plugin passthrough
-
A curated set of skills for each stage of development — propose, spec, design, plan, implement, ship.
-
Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.
-
10 slash commands and 3 agent definitions distilled from 6 months of daily Claude Code use. Not a framework -- just the patterns that survived: multi-agent build pipelines…
-
Autonomous Plan → Work → Review cycle for Claude Code. Go-native engine with 25× faster hooks, runtime guardrails on .git/ / secrets / destructive commands, and SSOT memory…
What each says it does
clio-coder-dev
Governs changes to Clio Coder's own source and harness (TUI, skills, agents, tools, prompts, domains): what may change freely, what needs explicit user intent, and how to change it without breaking the architecture. Not for verifying a change against the harness; use clio-coder-test.
Desktop Commander
MCP server for terminal commands, file operations, and process management
How to run each
clio-coder-dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Desktop Commander As a local MCP server: npm package
claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commanderCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of clio-coder-dev publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: clio-coder-dev · What it can do: Desktop Commander · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.