file-systemsdeveloper-tools

Desktop Commander

wonderwhy-er

by wonderwhy-er

Desktop Commander MCP unifies code management with advanced source control, git, and svn support—streamlining developmen

Desktop Commander MCP transforms Claude Desktop into a powerful AI assistant for managing files, running terminal commands, and editing code with precision across your entire system. It supports in-memory code execution, interactive process control, advanced search and replace, plus comprehensive filesystem operations including reading from URLs and negative offset file reads. With detailed audit and fuzzy search logging, it enables efficient automation, data analysis, and multi-project workflows—all without extra API costs. Designed for developers seeking smarter automation, it enhances productivity by integrating all essential development tools into a single, intelligent chat interface.

github stars

5.6K

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

No API costs - uses Claude Desktop subscriptionIn-memory code execution supportComprehensive audit logging

best for

  • / Developers automating file management and code editing
  • / System administrators running terminal commands via AI
  • / Data analysts processing files and extracting content
  • / Multi-project workflows requiring filesystem coordination

capabilities

  • / Read and write files from local paths or URLs
  • / Execute terminal commands and control processes
  • / Search across multiple files with fuzzy matching
  • / Create and manage directories and file structures
  • / Edit code with advanced search and replace operations
  • / Extract content from PDFs as markdown

what it does

Enables Claude Desktop to directly manage your filesystem, execute terminal commands, and edit code across your entire system. Provides comprehensive file operations, process control, and search capabilities through a chat interface.

about

Desktop Commander is an official MCP server published by wonderwhy-er that provides AI assistants with tools and capabilities via the Model Context Protocol. Desktop Commander MCP unifies code management with advanced source control, git, and svn support—streamlining developmen It is categorized under file systems, developer tools. This server exposes 26 tools that AI clients can invoke during conversations and coding sessions.

how to install

You can install Desktop Commander in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

Desktop Commander is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

Desktop Commander MCP

Search, update, manage files and run terminal commands with AI

npm downloads AgentAudit Verified Trust Score smithery badge Buy Me A Coffee

Discord

Work with code and text, run processes, and automate tasks, going far beyond other AI editors - while using host client subscriptions instead of API token costs.

<a href="https://glama.ai/mcp/servers/zempur9oh4"> <img width="380" height="200" src="https://glama.ai/mcp/servers/zempur9oh4/badge" alt="Desktop Commander MCP" /> </a>

👋 We’re hiring — come build with us: https://desktopcommander.app/careers/

🖥️ Try the Desktop Commander App (Beta)

Want a better experience? The Desktop Commander App gives you everything the MCP server does, plus:

  • Use any AI model — Claude, GPT-4.5, Gemini 2.5, or any model you prefer
  • See file changes live — visual file previews as AI edits your files
  • Add custom MCPs and context — extend with your own tools, no config files
  • Coming soon — skills system, dictation, background scheduled tasks, and more

👉 Download the App (macOS & Windows)

The MCP server below still works great with Claude Desktop and other MCP clients — the app is for those who want a dedicated, polished experience.

Table of Contents

All of your AI development tools in one place. Desktop Commander puts all dev tools in one chat. Execute long-running terminal commands on your computer and manage processes through Model Context Protocol (MCP). Built on top of MCP Filesystem Server to provide additional search and replace file editing capabilities.

Features

  • Remote AI Control - Use Desktop Commander from ChatGPT, Claude web, and other AI services via Remote MCP
  • File Preview UI - Visual file previews in Claude Desktop with rendered markdown, inline images, expandable content, and quick "Open in folder" access
  • Enhanced terminal commands with interactive process control
  • Execute code in memory (Python, Node.js, R) without saving files
  • Instant data analysis - just ask to analyze CSV/JSON/Excel files
  • Native Excel file support - Read, write, edit, and search Excel files (.xlsx, .xls, .xlsm) without external tools
  • PDF support - Read PDFs with text extraction, create new PDFs from markdown, modify existing PDFs
  • DOCX support - Read, create, edit, and search Word documents (.docx) with surgical XML editing and markdown-to-DOCX conversion
  • Interact with running processes (SSH, databases, development servers)
  • Execute terminal commands with output streaming
  • Command timeout and background execution support
  • Process management (list and kill processes)
  • Session management for long-running commands
  • Process output pagination - Read terminal output with offset/length controls to prevent context overflow
  • Server configuration management:
    • Get/set configuration values
    • Update multiple settings at once
    • Dynamic configuration changes without server restart
  • Full filesystem operations:
    • Read/write files (text, Excel, PDF, DOCX)
    • Create/list directories
    • Recursive directory listing with configurable depth and context overflow protection for large folders
    • Move files/directories
    • Search files and content (including Excel content)
    • Get file metadata
    • Negative offset file reading: Read from end of files using negative offset values (like Unix tail)
  • Code editing capabilities:
    • Surgical text replacements for small changes
    • Full file rewrites for major changes
    • Multiple file support
    • Pattern-based replacements
    • vscode-ripgrep based recursive code or text search in folders
  • Comprehensive audit logging:
    • All tool calls are automatically logged
    • Log rotation with 10MB size limit
    • Detailed timestamps and arguments
  • Security hardening:
    • Symlink traversal prevention on file operations
    • Command blocklist with bypass protection
    • Docker isolation for full sandboxing
    • See SECURITY.md for details

How to install

Install in Claude Desktop

Desktop Commander offers multiple installation methods for Claude Desktop.

📋 Update & Uninstall Information: Options 1, 2, 3, 4, and 6 have automatic updates. Option 5 requires manual updates. See below for details.

<details> <summary><b>Option 1: Install through npx ⭐ Auto-Updates (Requires Node.js)</b></summary>

Just run this in terminal:

npx @wonderwhy-er/desktop-commander@latest setup

For debugging mode (allows Node.js inspector connection):

npx @wonderwhy-er/desktop-commander@latest setup --debug

Command line options during setup:

  • --debug: Enable debugging mode for Node.js inspector
  • --no-onboarding: Disable onboarding prompts for new users

Restart Claude if running.

✅ Auto-Updates: Yes - automatically updates when you restart Claude
🔄 Manual Update: Run the setup command again
🗑️ Uninstall: Run npx @wonderwhy-er/desktop-commander@latest remove

</details> <details> <summary><b>Option 2: Using bash script installer (macOS) ⭐ Auto-Updates (Installs Node.js if needed)</b></summary>
curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install.sh | bash

This script handles all dependencies and configuration automatically.

✅ Auto-Updates: Yes
🔄 Manual Update: Re-run the bash installer command above
🗑️ Uninstall: Run npx @wonderwhy-er/desktop-commander@latest remove

</details> <details> <summary><b>Option 3: Installing via Smithery ⭐ Auto-Updates (Requires Node.js)</b></summary>
  1. Visit: https://smithery.ai/server/@wonderwhy-er/desktop-commander
  2. Login to Smithery if you haven't already
  3. Select your client (Claude Desktop) on the right side
  4. Install with the provided key that appears after selecting your client
  5. Restart Claude Desktop

✅ Auto-Updates: Yes - automatically updates when you restart Claude
🔄 Manual Update: Visit the Smithery page and reinstall

</details> <details> <summary><b>Option 4: Add to claude_desktop_config manually ⭐ Auto-Updates (Requires Node.js)</b></summary>

Add this entry to your claude_desktop_config.json:

  • On Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • On Windows: %APPDATA%\Claude\claude_desktop_config.json
  • On Linux: ~/.config/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": [
        "-y",
        "@wonderwhy-er/desktop-commander@latest"
      ]
    }
  }
}

Restart Claude if running.

✅ Auto-Updates: Yes - automatically updates when you restart Claude
🔄 Manual Update: Run the setup command again
🗑️ Uninstall: Run npx @wonderwhy-er/desktop-commander@latest remove or remove the entry from your claude_desktop_config.json

</details> <details> <summary><b>Option 5: Checkout locally ❌ Manual Updates (Requires Node.js)</b></summary>
git clone https://github.com/wonderwhy-er/DesktopCommanderMCP.git
cd DesktopCommanderMCP
npm run setup

Restart Claude if running.

The setup command will install dependencies, build the server, and configure Claude's desktop app.

❌ Auto-Updates: No - requires manual git updates
🔄 Manual Update: cd DesktopCommanderMCP && git pull && npm run setup
🗑️ Uninstall: Run npx @wonderwhy-er/desktop-commander@latest remove or remove the cloned directory and MCP server entry from Claude config

</details> <details> <summary><b>Option 6: Docker Installation 🐳 ⭐ Auto-Updates (No Node.js Required)</b></summary>

Perfect for users who want isolation or don't have Node.js installed. Runs in a sandboxed Docker container with a persistent work environment.

Prerequisites: Docker Desktop installed and running, Claude Desktop app installed.

macOS/Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh)

Windows PowerShell:

iex ((New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1'))

The installer will check Docker, pull the image, prompt for folder mounting, and configure Claude Desktop.

Docker persistence: Your tools, configs, work files, and package caches all survive restarts.

<details> <summary>Manual Docker Configuration</summary>

**Basic


FAQ

What is the Desktop Commander MCP server?
Desktop Commander is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Desktop Commander?
This profile displays 31 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.

Use Cases

Code & Document Analysis

Read, analyze, and understand files in your project

Example

Summarize README, analyze code structure, find TODO comments across codebase

Navigate large codebases 5x faster, understand projects quickly

Automated File Operations

Create, move, rename, and organize files based on natural language instructions

Example

Organize downloads by file type, rename files following convention, batch process images

Save hours on manual file organization

Content Search & Extraction

Search files for patterns, extract data, find information across directories

Example

Find all config files with API keys, extract emails from documents, search logs for errors

Find information instantly instead of manual grep/find

File Generation & Templates

Generate boilerplate files, apply templates, create project structures

Example

Create React component with tests and styles, generate OpenAPI spec, scaffold new project

Eliminate repetitive file creation work

Implementation Guide

Prerequisites

  • Claude Desktop or Cursor with MCP support
  • File system permissions for directories you want to access
  • Understanding of file paths and directory structure
  • Backup of important files before bulk operations

Time Estimate

10-20 minutes including configuration

Installation Steps

  1. 1.Install filesystem MCP server (often built-in with Claude Desktop)
  2. 2.Configure allowed directories in MCP config for security
  3. 3.Test read: 'Show me contents of ~/Documents/test.txt'
  4. 4.Test write: 'Create a new file notes.md in current directory'
  5. 5.Test search: 'Find all .js files containing TODO'
  6. 6.Test batch operations: 'Rename all .jpeg files to .jpg'
  7. 7.Verify file permissions and access controls

Troubleshooting

  • Permission denied: Check file/directory permissions, run with appropriate user
  • Path not found: Verify path is absolute or relative to working directory
  • MCP server can't access directory: Add to allowed directories in config
  • File already exists: Use overwrite flag or check before writing
  • Operation failed: Check disk space, file locks, antivirus interference

Best Practices

✓ Do

  • +Configure allowed directories explicitly—don't grant full filesystem access
  • +Back up important files before bulk operations
  • +Use dry-run mode for risky operations when available
  • +Validate file paths before operations
  • +Set appropriate file permissions on created files
  • +Log file operations for audit trail
  • +Test operations on sample files first

✗ Don't

  • Don't grant MCP access to system directories (/etc, /System)
  • Don't allow write access to production config files
  • Don't skip backup before bulk delete/move operations
  • Don't use for sensitive files (passwords, keys) without encryption
  • Don't ignore file permission errors—investigate root cause
  • Don't expose personal documents without considering privacy

💡 Pro Tips

  • Use .gitignore patterns to exclude sensitive files from AI access
  • Create sandboxed working directory for file experiments
  • Combine with version control (git) for easy rollback
  • Use file watching for real-time monitoring and reactions
  • Create templates for common file generation tasks
  • Leverage file metadata (timestamps, size) for smart organization

Technical Details

Architecture

MCP server provides file I/O operations (read, write, search, metadata) as tools Claude can invoke with natural language instructions.

Protocols

  • Local file system API
  • Glob patterns for search
  • File streams for large files

Compatibility

  • macOS
  • Linux
  • Windows
  • Local files only (no remote filesystems by default)

When to Use This

✓ Use When

Use for code analysis, file organization, content search, template generation, and automating repetitive file operations. Best for local development workflows.

✗ Avoid When

Avoid for system-critical files, sensitive credentials, production environments, or when file integrity is paramount. Don't use on files you can't afford to lose.

Integration

  • Combine with git for version-controlled file operations
  • Integrate with code editors for seamless workflow
  • Use with backup tools for safety net
  • Pair with file watchers for automated reactions

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.531 reviews
  • Sakura Huang· Dec 20, 2024

    Desktop Commander reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Chaitanya Patil· Dec 16, 2024

    Desktop Commander reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Ama Tandon· Nov 11, 2024

    I recommend Desktop Commander for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Piyush G· Nov 7, 2024

    I recommend Desktop Commander for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Shikha Mishra· Oct 26, 2024

    Strong directory entry: Desktop Commander surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Mateo Ndlovu· Oct 2, 2024

    Strong directory entry: Desktop Commander surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Kiara Ghosh· Sep 21, 2024

    Desktop Commander has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Yash Thakker· Sep 17, 2024

    Desktop Commander has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Isabella Shah· Sep 13, 2024

    We evaluated Desktop Commander against two servers with overlapping tools; this profile had the clearer scope statement.

  • Charlotte Srinivasan· Sep 5, 2024

    Desktop Commander reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

showing 1-10 of 31

1 / 4