Ext Ops Panel
Open dashboard
Comparison

Claude SOPs vs Desktop Commander

Claude SOPs is a plugin bundle for AI coding tools published by danielrosehill. 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: 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-18. 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 SOPsDesktop Commander
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 0.2.0
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 926 846
Downloads/week (npm): 204 381
Forks (GitHub): 1 281
Stars (GitHub): 10 089
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 281
Stars (GitHub): 10 089
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:5df787069e37
Forks (GitHub): 1 281
Pulls (Docker Hub): 237 140
Stars (Docker Hub): 22
Stars (GitHub): 10 089
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 281
Stars (GitHub): 10 089
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 281
Stars (GitHub): 10 089
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 SOPs vs Desktop Commander
FactClaude SOPsDesktop Commander
Marketplaces that list it (differs)1 (worse)6 (better)
Stars (GitHub) (differs)3 (worse)10 089 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub237 140
Forks (GitHub) (differs)1 (worse)1 281 (better)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleOn your machine (@wonderwhy-er/desktop-commander)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published26
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)87
LicenceMITMIT
Repository (differs)github.com/danielrosehill/claude-sopsgithub.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)23
First seen (differs)2026-10-152026-10-11

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 SOPs

In its own words, on Community GitHub marketplaces:

Keep your own standard operating procedures — the recurring things you do a particular way — as a private, versioned library of markdown files the agent reads on demand and follows. Distinct from sop-writer, which authors printed SOP documents for other people; these are procedures an agent executes. One delimited block in your CLAUDE.md points at the library, a generated INDEX.md carries id, title and a 'use when' trigger for each procedure, and exactly one file is read once a situation matches — so a library of forty procedures costs one table to consult rather than forty resident skill descriptions. Seven skills cover setup, run, write, edit, list, retire and sync. Procedures live in ~/.claude-user-data/sops/ as flat readable files inside a private git repo, mirrored across machines; the plugin repo never holds one. Each SOP declares an autonomy level (auto, confirm, confirm-each, manual) that records a default rather than granting permission, and a last_verified date meaning the procedure was seen to work

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 SOPs As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install sop-library@danielrosehill

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.

Tools each declares

The marketplaces of Claude SOPs 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: Claude SOPs · 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.

Where the data comes from: how the catalog is built