Ext Ops Panel
Open dashboard
Comparison

claude-forge vs Desktop Commander

claude-forge is a plugin bundle for AI coding tools published by Sangrok Jung. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-11-08. 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
Marketplaceclaude-forgeDesktop Commander
Community marketplace sangrokjung/claude-forge Listed
Version: 4.3.0
Forks (GitHub): 182
Stars (GitHub): 874
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.1
Downloads/month (npm): 1 386 176
Downloads/week (npm): 637 017
Forks (GitHub): 1 275
Stars (GitHub): 10 236
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 275
Stars (GitHub): 10 236
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:5df787069e37
Forks (GitHub): 1 275
Pulls (Docker Hub): 243 752
Stars (Docker Hub): 22
Stars (GitHub): 10 236
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 275
Stars (GitHub): 10 236
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 275
Stars (GitHub): 10 236
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.2.92
Downloads/month (npm): 1 864
Downloads/week (npm): 1 537
Forks (GitHub): 1 275
Stars (GitHub): 10 236
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

claude-forge vs Desktop Commander
Factclaude-forgeDesktop Commander
Marketplaces that list it (differs)1 (worse)7 (better)
Stars (GitHub) (differs)874 (worse)10 236 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub243 752
Forks (GitHub) (differs)182 (worse)1 275 (better)
Last release (differs)Not published2026-10-22
Where it runs (differs)Remote server (mcp.exa.ai/mcp)On your machine (@wonderwhy-er/desktop-commander)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published26
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)1027
LicenceMITMIT
Repository (differs)github.com/sangrokjung/claude-forgegithub.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)20
First seen (differs)2026-11-042026-10-11
Endpoint at the last check (differs)Responded 2 h agono 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

claude-forge

In its own words, on Community GitHub marketplaces:

Production-grade development environment for Claude Code with 16 specialized agents, 35 slash commands, 33 skills, 22 hooks + 9 opt-in examples (21 events), 14 rules, and 4 MCP servers (playwright, context7, jina-reader, chrome-devtools pinned at 0.23.0). Includes TDD workflow, security review, code review, architecture analysis, build error resolution, Chrome DevTools Lighthouse / Core Web Vitals audits, and an adversarial verification loop (maker≠checker) with unattended API-error auto-resume, session relay, and Korean prose quality guardrails.

Desktop Commander

In its own words, on Official MCP Registry:

MCP server for terminal commands, file operations, and process management

How to run each

claude-forge As a Claude Code plugin

Claude Code
/plugin marketplace add sangrokjung/claude-forge
/plugin install claude-forge@claude-forge

Desktop Commander As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commander

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

Only claude-forge has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of claude-forge publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: claude-forge · 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. 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.

Where the data comes from: how the catalog is built