Comparison

Rust Filesystem vs Desktop Commander

Rust Filesystem is an MCP server published by rust-mcp-stack. 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-18. 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	Rust Filesystem	Desktop Commander
Docker MCP Catalog	Listed Version: sha256:0a8d6879a676 Forks (GitHub): 29 Pulls (Docker Hub): 42 644 Stars (Docker Hub): 2 Stars (GitHub): 180 Not marked · First seen 2026-10-11	Listed Version: sha256:5df787069e37 Forks (GitHub): 1 281 Pulls (Docker Hub): 237 255 Stars (Docker Hub): 22 Stars (GitHub): 10 089 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 0.3.0 Downloads/month (npm): 966 995 Downloads/week (npm): 159 845 Forks (GitHub): 1 281 Stars (GitHub): 10 089 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-official	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 281 Stars (GitHub): 10 089 Not marked · First seen 2026-10-11
Claude: knowledge-work-plugins	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 281 Stars (GitHub): 10 089 Not marked · First seen 2026-10-11
Claude Code: claude-plugins-community	Not listed	Listed Version: 0.2.0 Forks (GitHub): 1 281 Stars (GitHub): 10 089 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

Rust Filesystem vs Desktop Commander
Fact	Rust Filesystem	Desktop Commander
Marketplaces that list it (differs)	1 (worse)	6 (better)
Stars (GitHub) (differs)	180 (worse)	10 089 (better)
Pulls (Docker Hub) (differs)	42 644 (worse)	237 255 (better)
Forks (GitHub) (differs)	29 (worse)	1 281 (better)
Last release (differs)	Not published	2026-10-13
Where it runs (differs)	On your machine (mcp/rust-mcp-filesystem)	On your machine (@wonderwhy-er/desktop-commander)
Transport	stdio	stdio
Tools it declares (differs)	24	26
Environment variables it asks for (differs)	2, secrets among them: 0	Not published
Parts of the bundle (differs)	Not a bundle	7
Licence	MIT	MIT
Repository (differs)	github.com/rust-mcp-stack/rust-mcp-filesystem	github.com/wonderwhy-er/desktopcommandermcp
Changes in the last 7 days (differs)	0	3
First seen	2026-10-11	2026-10-11

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

Rust Filesystem

In its own words, on Docker MCP Catalog:

The Rust MCP Filesystem is a high-performance, asynchronous, and lightweight Model Context Protocol (MCP) server built in Rust for secure and efficient filesystem operations. Designed with security in mind, it operates in read-only mode by default and restricts clients from updating allowed directories via MCP Roots unless explicitly enabled, ensuring robust protection against unauthorized access. Leveraging asynchronous I/O, it delivers blazingly fast performance with a minimal resource footprint. Optimized for token efficiency, the Rust MCP Filesystem enables large language models (LLMs) to precisely target searches and edits within specific sections of large files and restrict operations by file size range, making it ideal for efficient file exploration, automation, and system integration.

Desktop Commander

In its own words, on Official MCP Registry:

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

How to run each

Rust Filesystem As a local MCP server: Docker image

Claude Code

claude mcp add --transport stdio rust-mcp-filesystem -- docker run -i --rm mcp/rust-mcp-filesystem

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

Only Rust Filesystem declares

calculate_directory_size
directory_tree
edit_file
find_duplicate_files
find_empty_directories
head_file
list_allowed_directories
list_directory_with_sizes
read_file_lines
read_media_file
read_multiple_media_files
read_multiple_text_files

Show the remaining 7

read_text_file
search_files
search_files_content
tail_file
unzip_file
zip_directory
zip_files

Only Desktop Commander declares

edit_block
force_terminate
get_config
get_more_search_results
get_prompts
get_recent_tool_calls
get_usage_stats
give_feedback_to_desktop_commander
interact_with_process
kill_process
list_processes
list_searches

Show the remaining 9

list_sessions
read_file
read_multiple_files
read_process_output
set_config_value
start_process
start_search
stop_search
write_pdf

Both declare

create_directory
get_file_info
list_directory
move_file
write_file

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

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

What it can do: Rust Filesystem · 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-18. We publish no contact details for plugin publishers.