Comparison

Indiana Code vs Desktop Commander

Indiana Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). 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. 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	Indiana Code	Desktop Commander
Official MCP Registry	Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11	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 2026-10-11
Claude Code: claude-plugins-official	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen 2026-10-11
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 2026-10-11
Claude: knowledge-work-plugins	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-community	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 268 Stars (GitHub): 10 146 Not marked · First seen 2026-10-11
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 2026-10-12

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

Indiana Code vs Desktop Commander
Fact	Indiana Code	Desktop Commander
Marketplaces that list it (differs)	1 (worse)	7 (better)
Stars (GitHub) (differs)	0 (worse)	10 146 (better)
Pulls (Docker Hub) (differs)	No figure on Docker Hub	240 629
Forks (GitHub) (differs)	0 (worse)	1 268 (better)
Last release (differs)	2026-10-29 (better)	2026-10-22 (worse)
Where it runs (differs)	Remote server (gateway.pipeworx.io/indiana-code/mcp)	On your machine (@wonderwhy-er/desktop-commander)
Transport (differs)	Streamable HTTP	stdio
Tools it declares (differs)	Not published	26
Environment variables it asks for (differs)	1, secrets among them: 1	Not published
Parts of the bundle (differs)	Not a bundle	7
Licence (differs)	Not stated	MIT
Repository (differs)	github.com/pipeworx-io/mcp-indiana-code	github.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)	4	1
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	Responded 10 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

Indiana Code

In its own words, on Official MCP Registry:

Indiana Code — state statutes by citation, plus topic search and historical (per-year) versions.…

Desktop Commander

In its own words, on Official MCP Registry:

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

How to run each

Indiana Code As a remote MCP server

Claude Code

claude mcp add --transport http indiana-code https://gateway.pipeworx.io/indiana-code/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Tools each declares

Only Indiana Code has

ai_visibility_check
archive_compare
archive_evidence
ask_pipeworx
ask_pipeworx_beta
ask_pipeworx_grounded
bet_research
classify_row
company_facts
company_register_search
compare_entities
deep_research

Show the remaining 31

discover_tools
entity_profile
forget
generate_llms_txt
in_code_search
in_code_section
kalshi_weather_edge
list_subscriptions
pipeworx_feedback
pipeworx_trending
polymarket_arbitrage
polymarket_edge_tracker
polymarket_edges
polymarket_fill_risk
polymarket_kalshi_spread
recall
recent_alerts
recent_changes
release_calendar_markets
remember
research_row
resolution_audit
resolution_diff
resolve_entity
scan_competitor_ai_presence
scan_dependency
search_within
subscribe
suggest_questions
unsubscribe
validate_claim

Only Desktop Commander has

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 have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Indiana Code as of 2026-10-20). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Desktop Commander publish no settings it asks for, so we do not compare settings.

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

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. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on 2026-10-29. We publish no contact details for plugin publishers.