Comparison

GitMCP vs Desktop Commander

GitMCP is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-15. 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
Marketplace	GitMCP	Desktop Commander
Docker MCP Catalog	Listed Version: not stated No figure published Not marked · First seen 2026-10-11	Listed Version: sha256:5df787069e37 Forks (GitHub): 1 272 Pulls (Docker Hub): 236 074 Stars (Docker Hub): 22 Stars (GitHub): 10 050 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 0.3.0 Downloads/month (npm): 926 846 Downloads/week (npm): 204 381 Forks (GitHub): 1 272 Stars (GitHub): 10 050 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-official	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 272 Stars (GitHub): 10 050 Not marked · First seen 2026-10-11
Claude: knowledge-work-plugins	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 272 Stars (GitHub): 10 050 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-community	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 272 Stars (GitHub): 10 050 Not marked · First seen 2026-10-11

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

GitMCP vs Desktop Commander
Fact	GitMCP	Desktop Commander
Marketplaces that list it (differs)	1 (worse)	6 (better)
Stars (GitHub) (differs)	No figure on GitHub	10 050
Pulls (Docker Hub) (differs)	No figure on Docker Hub	236 074
Forks (GitHub) (differs)	No figure on GitHub	1 272
Last release (differs)	Not published	2026-10-13
Where it runs (differs)	Remote server (gitmcp.io/docs)	On your machine (@wonderwhy-er/desktop-commander)
Transport (differs)	Streamable HTTP	stdio
Tools it declares (differs)	5	26
Environment variables it asks for	Not published	Not published
Parts of the bundle (differs)	Not a bundle	7
Licence (differs)	Apache-2.0	MIT
Repository (differs)	Not stated	github.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)	0	3
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	Responded 19 h ago	no 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

GitMCP

In its own words, on Docker MCP Catalog:

Tools for interacting with Git repositories.

Desktop Commander

In its own words, on Official MCP Registry:

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

How to run each

GitMCP As a remote MCP server

Claude Code

claude mcp add --transport http gitmcp https://gitmcp.io/docs

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 GitMCP has a remote endpoint we check. How we check endpoints

Tools each declares

Only GitMCP declares

fetch_generic_documentation
fetch_generic_url_content
match_common_libs_owner_repo_mapping
search_generic_code
search_generic_documentation

Only Desktop Commander declares

create_directory
edit_block
force_terminate
get_config
get_file_info
get_more_search_results
get_prompts
get_recent_tool_calls
get_usage_stats
give_feedback_to_desktop_commander
interact_with_process
kill_process

Show the remaining 14

list_directory
list_processes
list_searches
list_sessions
move_file
read_file
read_multiple_files
read_process_output
set_config_value
start_process
start_search
stop_search
write_file
write_pdf

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: GitMCP · What it can do: Desktop Commander · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on 2026-10-15. We publish no contact details for plugin publishers.