Desktop Commander MCP

MCP serverFiles & storage

desktop-commander connects your AI to your computer. Once it is added, your AI can run terminal commands, manage files, and control running processes, so you can hand computer tasks to your AI instead of doing them yourself.

Available today. Use it from your connected AI after setup.

Add desktop-commander, then ask your AI to run a command, work with a file, or check on something running on your machine. It will take care of it while you stay in the conversation.

Then ask your AI: use Desktop Commander MCP

What your AI can do with it

  • Run terminal commands on your computer
  • Manage files on your computer
  • Control processes that are running on your computer
  • Carry out tasks that mix commands, files, and running programs in one go

From the project's README

As published by wonderwhy-er/desktopcommandermcp in README.md.

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

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.

πŸ–₯️ 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

  • Features
  • How to install
  • Getting Started
  • Usage
  • File Preview UI & Markdown Editor
  • Handling Long-Running Commands
  • Work in Progress and TODOs
  • Sponsors and Supporters
  • Website
  • Media
  • Testimonials
  • Frequently Asked Questions
  • Contributing
  • License

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, built-in markdown editor, 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
  • Local tool-call history and audit logs:
    • Tool calls and arguments are recorded locally on the machine running Desktop Commander
    • Recent call history with bounded output previews is available through get_recent_tool_calls
    • Size-based rotation/trimming keeps the active history files bounded
  • Safety guardrails (not a sandbox β€” see SECURITY.md):
    • Symlink traversal prevention on file operations
    • Command blocklist for accidental execution
    • Docker isolation for complete isolation

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.

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

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

  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

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

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

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.

Basic setup (no file access):

{
  "mcpServers": {
    "desktop-commander-in-docker": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "mcp/desktop-commander:latest"]
    }
  }
}

With folder mounting:

{
  "mcpServers": {
    "desktop-commander-in-docker": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "/Users/username/Desktop:/mnt/desktop",
        "-v", "/Users/username/Documents:/mnt/documents",
        "mcp/desktop-commander:latest"
      ]
    }
  }
}

Advanced folder mounting:

{
  "mcpServers": {
    "desktop-commander-in-docker": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "dc-system:/usr",
        "-v", "dc-home:/root", 
        "-v", "dc-workspace:/workspace",
        "-v", "dc-packages:/var",
        "-v", "/Users/username/Projects:/mnt/Projects",
        "-v", "/Users/username/Downloads:/mnt/Downloads",
        "mcp/desktop-commander:latest"
      ]
    }
  }
}

macOS/Linux:

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

# Reset all persistent data
bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh) --reset

Windows PowerShell:

# Check status
$script = (New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1'); & ([ScriptBlock]::Create("$script")) -Status

# Reset all data
$script = (New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1'); & ([ScriptBlock]::Create("$script")) -Reset

# Show help
$script = (New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1'); & ([ScriptBlock]::Create("$script")) -Help

Troubleshooting: Reset and reinstall from scratch:

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

βœ… Auto-Updates: Yes - latest tag automatically gets newer versions
πŸ”„ Manual Update: docker pull mcp/desktop-commander:latest then restart Claude

Install in Other Clients

Desktop Commander works with any MCP-compatible client. The standard JSON configuration is:

{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": ["-y", "@wonderwhy-er/desktop-commander@latest"]
    }
  }
}

Add this to your client's MCP configuration file at the locations below:

View MCP Server in Directory

Or add manually to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project folder (project-specific).

See Cursor MCP docs for more info.

Add to ~/.codeium/windsurf/mcp_config.json. See Windsurf MCP docs for more info.

Add to .vscode/mcp.json in your project or VS Code User Settings (JSON). Make sure MCP is enabled under Chat > MCP. Works in Agent mode.

See VS Code MCP docs for more info.

Configure through the Cline extension settings in VS Code. Open the Cline sidebar, click the MCP Servers icon, and add the JSON configuration above. See Cline MCP docs for more info.

Add to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.

claude mcp add --scope user desktop-commander -- npx -y @wonderwhy-er/desktop-commander@latest

Remove --scope user to install for the current project only. See Claude Code MCP docs for more info.

Use the "Add manually" feature and paste the JSON configuration above. See Trae MCP docs for more info.

Navigate to Kiro > MCP Servers, click + Add, and paste the JSON configuration above. See Kiro MCP docs for more info.

Codex uses TOML configuration. Run this command to add Desktop Commander:

codex mcp add desktop-commander -- npx -y @wonderwhy-er/desktop-commander@latest

Or manually add to ~/.codex/config.toml:

[mcp_servers.desktop-commander]
command = "npx"
args = ["-y", "@wonderwhy-er/desktop-commander@latest"]

See Codex MCP docs for more info.

In JetBrains IDEs, go to Settings β†’ Tools β†’ AI Assistant β†’ Model Context Protocol (MCP), click + Add, select As JSON, and paste the JSON configuration above. See JetBrains MCP docs for more info.

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": ["-y", "@wonderwhy-er/desktop-commander@latest"]
    }
  }
}

See Gemini CLI docs for more info.

Press Cmd/Ctrl+Shift+P, open the Augment panel, and add a new MCP server named desktop-commander with the JSON configuration above. See Augment Code MCP docs for more info.

Run this command to add Desktop Commander:

qwen mcp add desktop-commander -- npx -y @wonderwhy-er/desktop-commander@latest

Or add to .qwen/settings.json (project) or ~/.qwen/settings.json (global). See Qwen Code MCP docs for more info.

Use Desktop Commander from ChatGPT, Claude web, and other AI services via Remote MCP β€” no desktop app required.

πŸ‘‰ Get started at mcp.desktopcommander.app

How it works:

  1. You run a lightweight Remote Device on your computer
  2. It connects securely to the cloud Remote MCP service
  3. Your AI sends commands through the cloud to your device
  4. Commands execute locally, results return to your AI
  5. You stay in control β€” stop anytime with Ctrl+C

Security

  • βœ… Device only runs when you start it
  • βœ… Commands execute under your user permissions
  • βœ… Secure OAuth authentication and encrypted communication channel

Updating & Uninstalling Desktop Commander

Automatic Updates (Options 1, 2, 3, 4 & 6)

Options 1 (npx), Option 2 (bash installer), 3 (Smithery), 4 (manual config), and 6 (Docker) automatically update to the latest version whenever you restart Claude. No manual intervention needed.

Manual Updates (Option 5)

  • Option 5 (local checkout): cd DesktopCommanderMCP && git pull && npm run setup

Uninstalling Desktop Commander

πŸ€– Automatic Uninstallation (Recommended)

The easiest way to completely remove Desktop Commander:

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

This automatic uninstaller will:

  • βœ… Remove Desktop Commander from Claude's MCP server configuration
  • βœ… Create a backup of your Claude config before making changes
  • βœ… Provide guidance for complete package removal
  • βœ… Restore from backup if anything goes wrong
πŸ”§ Manual Uninstallation

If the automatic uninstaller doesn't work or you prefer manual removal:

Remove from Claude Configuration
  1. Locate your Claude Desktop config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
  1. Edit the config file:
  • Open the file in a text editor
  • Find and remove the "desktop-commander" entry from the "mcpServers" section
  • Save the file

Example - Remove this section:

{
    "desktop-commander": {
      "command": "npx",
      "args": ["@wonderwhy-er/desktop-commander@latest"]
    }
}

Close and restart Claude Desktop to complete the removal.

πŸ†˜ Troubleshooting

If automatic uninstallation fails:

  • Use manual uninstallation as a fallback

If Claude won't start after uninstalling:

  • Restore the backup config file created by the uninstaller
  • Or manually fix the JSON syntax in your claude_desktop_config.json

Need help?

Getting Started

Once Desktop Commander is installed and Claude Desktop is restarted, you're ready to supercharge your Claude experience!

πŸš€ New User Onboarding

Desktop Commander includes intelligent onboarding to help you discover what's possible:

For New Users: When you're just getting started (fewer than 10 successful commands), Claude will automatically offer helpful getting-started guidance and practical tutorials after you use Desktop Commander successfully.

Request Help Anytime: You can ask for onboarding assistance at any time by simply saying:

  • "Help me get started with Desktop Commander"
  • "Show me Desktop Commander examples"
  • "What can I do with Desktop Commander?"

Claude will then show you beginner-friendly tutorials and examples, including:

  • πŸ“ Organizing your Downloads folder automatically
  • πŸ“Š Analyzing CSV/Excel files with Python
  • βš™οΈ Setting up GitHub Actions CI/CD
  • πŸ” Exploring and understanding codebases
  • πŸ€– Running interactive development environments

Usage

The server provides a comprehensive set of tools organized into several categories:

Available Tools

Shortened here. Read the whole README on GitHub.

Signals

GitHub stars
10k
Forks
1k
Last commit
Sep 2026
Advanced
Delivery
desktop-commander MCP server β†’ your ahel gateway (mcp.ahel.ai) β†’ every connected AI client.
Catalog kind
mcp-server
Gateway key
io-github-wonderwhy-er-desktop-commander
Source
github.com/wonderwhy-er/desktopcommandermcp