Ext Ops Panel
Open dashboard
Comparison

github-issue-worktree vs Desktop Commander

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

github-issue-worktree is a plugin bundle for AI coding tools published by gabrielkoerich. 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-21. 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
Marketplacegithub-issue-worktreeDesktop Commander
Community marketplace gabrielkoerich/skills Removed on 2026-10-21
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 966 995
Downloads/week (npm): 159 845
Forks (GitHub): 1 290
Stars (GitHub): 10 105
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 290
Stars (GitHub): 10 105
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:5df787069e37
Forks (GitHub): 1 290
Pulls (Docker Hub): 237 976
Stars (Docker Hub): 22
Stars (GitHub): 10 105
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 290
Stars (GitHub): 10 105
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 1 290
Stars (GitHub): 10 105
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

github-issue-worktree vs Desktop Commander
Factgithub-issue-worktreeno longer listed · Desktop Commander
Marketplaces that list it (differs)06
Stars (GitHub) (differs)610 105
Pulls (Docker Hub) (differs)No figure on Docker Hub237 976
Forks (GitHub) (differs)01 290
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)Not published7
Licence (differs)Not statedMIT
Repository (differs)github.com/gabrielkoerich/skillsgithub.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)50
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 github-issue-worktree

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

  • github-workflow

    GitHub workflow: issues, PRs, worktrees, sub-issues

    by Danil Pismenny · Plugin bundle

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

  • worktree-manager

    Effortless git worktrees for parallel development with automatic environment setup

    by Daniel Raffel · Plugin bundle

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

  • create-worktrees

    Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.

    by DevsForge Community · Plugin bundle

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

  • create-worktrees

    Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.

    by evmts · Plugin bundle

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

  • issue-to-pr

    Take GitHub issues to reviewed pull requests through isolated worktrees, tests, and explicit merge gates.

    by Dmitry Yuhanov · Plugin bundle

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

  • worktrees

    A band above the prompt with the git worktrees of the current repo: branch, uncommitted changes, and the count against a limit of 10.

    by fcsouza · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

github-issue-worktree

In its own words, on Community GitHub marketplaces:

Manage an isolated worktree per GitHub issue. Register the branch with `gh issue develop`, then create, list, and remove the worktree with `git cow` only, by following the git-worktrees skill. The default directory is `~/.worktrees/<project>/`. Use it when the user explicitly asks to work on a GitHub issue.

Desktop Commander

In its own words, on Official MCP Registry:

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

How to run each

github-issue-worktree

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 github-issue-worktree 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: github-issue-worktree · 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