Ext Ops Panel
Open dashboard
Comparison

conductor vs Desktop Commander

conductor is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑29.

conductor is a plugin bundle for AI coding tools published by Bryan Lackey. No marketplace we read lists it any more. 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. 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

Where each is published
MarketplaceconductorDesktop Commander
Community marketplace lackeyjb/claude-conductor Removed on 2026-10-29
Version: 1.2.0
Forks (GitHub): 2
Stars (GitHub): 15
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 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

conductor vs Desktop Commander
Factconductorno longer listed · Desktop Commander
Marketplaces that list it (differs)07
Stars (GitHub) (differs)1510 146
Pulls (Docker Hub) (differs)No figure on Docker Hub240 629
Forks (GitHub) (differs)21 268
Last release (differs)Not published2026-10-22
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
Hooks it runs (differs)4Not published
Parts of the bundle (differs)167
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/lackeyjb/claude-conductorgithub.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)32
First seen (differs)2026-10-262026-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 conductor

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • harness-boot

    Multi-agent development harness for Claude Code. Your AI has speed; we give it direction — through living specs and focused specialist agents.

    by qwerfunch · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-code-sdlc

    Turn Claude Code into an autonomous software development team — 16 specialized agents, documentation-first pipeline, TDD slices in parallel waves, and 9 quality gates.

    by Aleksei Korobeinikov · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • sdd

    Story Driven Development workflow for Claude Code. Keeps your documentation and code in sync via status tracking and git-diff-based prompts.

    by applica-software-guru · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • spec-to-code

    Accelerates software delivery by automating SDLC stages inside Claude Code — Claude facilitates writing specs and designing architecture, then autonomously builds implementation…

    by vkroz · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • flow

    Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and OKF knowledge bundles.

    by cofin · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • tdg

    Test-Driven Generation plugin for Claude Code

    by Chanwit Kaewkasi · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

conductor

In its own words, on Community GitHub marketplaces:

Context-Driven Development framework for Claude Code

Desktop Commander

In its own words, on Official MCP Registry:

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

How to run each

conductor

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 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 conductor 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: conductor · 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