Comparison

Desktop Commander vs Scriptura

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)). Scriptura is an MCP server published by scriptura.si. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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	Desktop Commander	Scriptura
Official MCP Registry	Listed Version: 0.3.1 Downloads/month (npm): 1 386 176 Downloads/week (npm): 637 017 Forks (GitHub): 1 275 Stars (GitHub): 10 236 Not marked · First seen 2026-10-11	Listed Version: 1.0.1 No figure published Not marked · First seen 2026-10-25
Claude Code: claude-plugins-official	Listed Version: 0.2.0 Forks (GitHub): 1 275 Stars (GitHub): 10 236 Not marked · First seen 2026-10-11	Not listed
Docker MCP Catalog	Listed Version: sha256:5df787069e37 Forks (GitHub): 1 275 Pulls (Docker Hub): 243 752 Stars (Docker Hub): 22 Stars (GitHub): 10 236 Not marked · First seen 2026-10-11	Not listed
Claude: knowledge-work-plugins	Listed Version: 0.2.0 Forks (GitHub): 1 275 Stars (GitHub): 10 236 Not marked · First seen 2026-10-11	Not listed
Claude Code: claude-plugins-community	Listed Version: 0.2.0 Forks (GitHub): 1 275 Stars (GitHub): 10 236 Not marked · First seen 2026-10-11	Not listed
npm registry (MCP servers)	Listed Version: 0.2.92 Downloads/month (npm): 1 864 Downloads/week (npm): 1 537 Forks (GitHub): 1 275 Stars (GitHub): 10 236 Not marked · First seen 2026-10-12	Not listed

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

Desktop Commander vs Scriptura
Fact	Desktop Commander	Scriptura
Marketplaces that list it (differs)	7 (better)	1 (worse)
Stars (GitHub) (differs)	10 236	No figure on GitHub
Pulls (Docker Hub) (differs)	243 752	No figure on Docker Hub
Forks (GitHub) (differs)	1 275	No figure on GitHub
Last release (differs)	2026-10-22 (worse)	2026-10-25 (better)
Where it runs (differs)	On your machine (@wonderwhy-er/desktop-commander)	Remote server (scriptura.si/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	26	Not published
Environment variables it asks for	Not published	Not published
Parts of the bundle (differs)	7	Not a bundle
Licence (differs)	MIT	Not stated
Repository (differs)	github.com/wonderwhy-er/desktopcommandermcp	Not stated
Changes in the last 7 days	0	0
First seen (differs)	2026-10-11	2026-10-25
Endpoint at the last check (differs)	no remote endpoint we check	Status out of date: last check 42 h ago returned HTTP 200

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

Desktop Commander

In its own words, on Official MCP Registry:

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

Scriptura

In its own words, on Official MCP Registry:

953 classic works in the original beside English: Greek, Latin, philosophy, literature, scripture

How to run each

Desktop Commander As a local MCP server: npm package

Claude Code

claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commander

Scriptura As a remote MCP server

Claude Code

claude mcp add --transport http scriptura https://scriptura.si/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Scriptura has a remote endpoint we check. How we check endpoints

Tools each declares

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

Only Scriptura has

get_passage
list_editions
read_work
room
search_shelf
who_read_verse

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Scriptura as of 2026-11-06). 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: Desktop Commander · What it can do: Scriptura · 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-11-08. We publish no contact details for plugin publishers.