Alaska Code vs Desktop Commander
Alaska 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: 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. 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
| Marketplace |  Alaska Code |   Desktop Commander |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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 149 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
| Fact | Alaska Code | Desktop Commander |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 6 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 10 129 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 240 149 |
| Forks (GitHub) (differs) | 0 (worse) | 1 263 (better) |
| Last release (differs) | 2026-10-22 (better) | 2026-10-22 (worse) |
| Where it runs (differs) | Remote server (gateway.pipeworx.io/alaska-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 | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 7 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/pipeworx-io/mcp-alaska-code | github.com/wonderwhy-er/desktopcommandermcp |
| Changes in the last 7 days | 1 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days 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
Alaska Code
Alaska Statutes — statute text by citation and chapter-catchline search. Fleet #2795.
Desktop Commander
MCP server for terminal commands, file operations, and process management
How to run each
Alaska Code As a remote MCP server
claude mcp add --transport http alaska-code https://gateway.pipeworx.io/alaska-code/mcpDesktop Commander As a local MCP server: npm package
claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commanderCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Alaska Code has a remote endpoint we check. How we check endpoints
Tools each declares
Only Alaska Code has
ai_visibility_checkak_searchak_statutearchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_search
Show the remaining 32
compare_entitiesdeep_researchdiscover_toolsentity_profileforgetgenerate_llms_txtkalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadprediction_calibrationrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Only Desktop Commander has
create_directoryedit_blockforce_terminateget_configget_file_infoget_more_search_resultsget_promptsget_recent_tool_callsget_usage_statsgive_feedback_to_desktop_commanderinteract_with_processkill_process
Show the remaining 14
list_directorylist_processeslist_searcheslist_sessionsmove_fileread_fileread_multiple_filesread_process_outputset_config_valuestart_processstart_searchstop_searchwrite_filewrite_pdf
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Alaska Code as of 2026-10-24). 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: Alaska 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.