Vibe Coding Control vs Desktop Commander
Vibe Coding Control is an MCP server published by OMNOM-111. Marketplaces we read that list it: 1 (Official MCP Registry). Desktop Commander is an MCP server published by wonderwhy-er. Marketplaces we read that list it: 7 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
| Marketplace |   Vibe Coding Control |   Desktop Commander |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.1 Downloads/month (npm): 1 386 176 Downloads/week (npm): 637 017 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:5df787069e37 Forks (GitHub): 1 268 Pulls (Docker Hub): 240 629 Stars (Docker Hub): 22 Stars (GitHub): 10 146 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 1 386 176 Downloads/week (npm): 637 017 Forks (GitHub): 1 268 Stars (GitHub): 10 146 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 | Vibe Coding Control | Desktop Commander |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 7 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 10 146 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 240 629 |
| Forks (GitHub) (differs) | 0 (worse) | 1 268 (better) |
| Last release (differs) | 2026-10-15 (worse) | 2026-10-22 (better) |
| Where it runs (differs) | Remote server (vibecodingcontrol.com/mcp) | On your machine (@wonderwhy-er/desktop-commander) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 26 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 7 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/omnom-111/vcc-remote | github.com/wonderwhy-er/desktopcommandermcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago, requires a key | no remote endpoint we check |
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
Vibe Coding Control
Your VCC projects, tasks, AI development history and owner decisions. Sign in with your VCC account.
Desktop Commander
MCP server for terminal commands, file operations, and process management
How to run each
Vibe Coding Control As a remote MCP server
claude mcp add --transport http vcc-remote https://vibecodingcontrol.com/mcpDesktop 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.
Only Vibe Coding Control has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Vibe Coding Control 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: Vibe Coding Control · What it can do: Desktop Commander · Compare two other plugins
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. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.