Ext Ops Panel
Open dashboard
Comparison

gemini-pair-pipeline vs Desktop Commander

gemini-pair-pipeline is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.

gemini-pair-pipeline is a plugin bundle for AI coding tools published by Community Contributors. 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-27. 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
Marketplacegemini-pair-pipelineDesktop Commander
Community marketplace gantisstorm/claude-code-pair-planning-framework Removed on 2026-10-21
Version: 1.3.0
Forks (GitHub): 1
Stars (GitHub): 6
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 263
Stars (GitHub): 10 129
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 263
Stars (GitHub): 10 129
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:5df787069e37
Forks (GitHub): 1 263
Pulls (Docker Hub): 240 270
Stars (Docker Hub): 22
Stars (GitHub): 10 129
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 263
Stars (GitHub): 10 129
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 263
Stars (GitHub): 10 129
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

gemini-pair-pipeline vs Desktop Commander
Factgemini-pair-pipelineno longer listed · Desktop Commander
Marketplaces that list it (differs)06
Stars (GitHub) (differs)610 129
Pulls (Docker Hub) (differs)No figure on Docker Hub240 270
Forks (GitHub) (differs)11 263
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
Parts of the bundle (differs)87
Licence (differs)Not statedMIT
Repository (differs)github.com/gantisstorm/claude-code-pair-planning-frameworkgithub.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)21
First seen (differs)2026-10-192026-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 gemini-pair-pipeline

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

  • superpipelines

    Multi-agent AI pipelines with structural write/review isolation, crash-safe state recovery, and spec-driven development. Run sequential, parallel fan-out, iterative-loop, or…

    by gustavo-meilus · Plugin bundle

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

  • ucai

    Structured workflows, parallel agents, hooks, and skills using Claude Code's native architecture.

    by Ucai · Plugin bundle

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

  • agent-runway

    Prevents subagent tech debt by injecting project architectural context (module boundaries, CLAUDE.md rules, conventions) into every subagent's prompt. Validates code placement and…

    by rennf93 · Plugin bundle

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

  • multi-agent-ops

    Self-correcting loop engineering and automated codebase research.

    by jggomez · Plugin bundle

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

  • aide

    AI Development Environment - Multi-agent orchestration for Claude Code

    by John Mylchreest · Plugin bundle

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

  • nexus-agents

    Intelligent orchestration platform for AI coding tools. Coordinates Claude, Codex, Gemini, and OpenCode through a single MCP server — routing each task to the best model using…

    by williamzujkowski · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

gemini-pair-pipeline

In its own words, on Community GitHub marketplaces:

Multi-agent orchestration for complex coding tasks with Gemini CLI (gemini-3-flash-preview). Scouts gather raw context, planners synthesize XML architectural instructions. Returns full plan with per-file instructions. Iterative discovery with user checkpoints and parallel execution. Session continuation via -r flag.

Desktop Commander

In its own words, on Official MCP Registry:

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

How to run each

gemini-pair-pipeline

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 gemini-pair-pipeline 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: gemini-pair-pipeline · 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