Desktop Commander MCP: Terminal, Filesystem, and Surgical Edits for Claude
Desktop Commander MCP v0.2.45 — 7.8k-star wonderwhy-er server for terminal control, ripgrep search, edit_block diffs, Excel/PDF/DOCX, and Claude Desktop file preview UI. Install for Cursor, Claude Code, Codex.
Desktop Commander MCP is the 7.8k-star open-source server that turns Claude into something closer to a human developer on your machine — terminal sessions, ripgrep search, surgical edit_block patches, Excel/PDF/DOCX, and a file preview UI in Claude Desktop. Latest release: v0.2.45 (July 11, 2026).
Creator @wonderwhy-er (Eduard Ruzga) built it on top of Anthropic's MCP Filesystem Server and extended it far beyond read/write — the README's pitch: "Work with code and text, run processes, and automate tasks… using host client subscriptions instead of API token costs."
Claude Desktop · Cursor · Claude Code · Codex · Gemini CLI · Remote MCP
Why Desktop Commander exists
Before MCP, Claude could only see what you pasted. IDE agents like Cursor and Windsurf added filesystem + terminal — but burn fast-request quotas and chunk large files.
Desktop Commander's differentiation (from the README and community testimonials):
Pain
Desktop Commander answer
API/token burn
Runs on Claude Pro subscription — not per-call API
IDE lock-in
Works across OS-wide projects, not one repo
Chunked file reads
Full-file reads with pagination + negative offset (tail)
Cascade rewrites
edit_block surgical patches + 50-line write cap by default
No terminal REPL
start_process + interact_with_process for SSH, Node, Python
YouTube commenters in the repo describe ditching Cursor + Claude duplicate subscriptions and fixing a Flutter null-safety migration in hours after days stuck in IDE cascades.
Interactive tree — lazy load, click-to-preview, Open in Finder
PDF / Excel / DOCX
Native extraction display
Directory browser:list_directory opens as expandable tree inside the panel — not a wall of paths in chat.
Pair with Claude Code desktop browser when you need web verification; Desktop Commander handles local disk + terminal.
Quick workflows
Data analysis (in-memory)
"Analyze sales.csv and show top customers"
Desktop Commander runs Python in memory — no temp script file on disk.
SSH + ops
"SSH to my server and check disk space"
start_process maintains the SSH session; interact_with_process sends follow-up commands.
Surgical refactor
"Replace deprecated API calls in src/api/.ts"*
start_search → ripgrep hits → multiple small edit_block patches (not one 2,000-line rewrite).
Onboarding
New users (<10 successful commands) get automatic tutorials. Anytime:
"Help me get started with Desktop Commander"
"Show me Desktop Commander examples"
Disable: --no-onboarding flag in npx args.
Desktop Commander vs Cursor / Windsurf / Claude Code
Dimension
Desktop Commander
Cursor / Windsurf
Claude Code (native)
Billing
Host subscription
Fast requests / credits
Anthropic plan quota
Scope
Entire OS
Single workspace
Project directory
Terminal
Interactive sessions + pagination
Integrated terminal
Bash tool
Edits
edit_block + fuzzy logs
Multi-file agent
Write + native Edit
Preview UI
Claude Desktop widget
IDE diff view
Terminal output
Excel/PDF/DOCX
Native tools
Limited / extensions
Not built-in
explainx.ai read: Desktop Commander is not a Cursor replacement — it's the MCP layer that makes Claude Desktop (or any MCP host) competitive with IDE agents for subscription-priced automation. Many teams run Codex vs Claude Code for repo work and Desktop Commander for OS-wide scripts.
The MCP server remains the path for Claude Desktop / Cursor / Codex users who want the open-source integration.
Remote MCP
Desktop Commander supports Remote MCP — use from ChatGPT web and Claude web without local Claude Desktop. Same tool surface; latency and sandbox policy depend on the remote host.
Desktop Commander runs with your user permissions. Treat it like installing a global npm CLI with full disk and shell access — use Docker or tight allowedDirectories on shared machines.
