Desktop Commander MCP

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

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 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"

      ]

    }

  }

}

</details>

<details>
<summary>Docker Management Commands</summary>

macOS/Linux:

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

json
{
"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:

<details>

<summary><b>Cursor</b></summary><br>

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.
</details>
<details>

<summary><b>Windsurf</b></summary>
Add to ~/.codeium/windsurf/mcp_config.json. See Windsurf MCP docs for more info.
</details>
<details>

<summary><b>VS Code / GitHub Copilot</b></summary>
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.
</details>
<details>

<summary><b>Cline</b></summary>
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.
</details>
<details>

<summary><b>Roo Code</b></summary>
Add to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.
</details>
<details>

<summary><b>Claude Code</b></summary>

sh
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.

</details>
<details>

<summary><b>Trae</b></summary>
Use the "Add manually" feature and paste the JSON configuration above. See Trae MCP docs for more info.
</details>
<details>

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

<summary><b>Codex (OpenAI)</b></summary>
Codex uses TOML configuration. Run this command to add Desktop Commander:

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

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

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

See Codex MCP docs for more info.

</details>
<details>

<summary><b>JetBrains (AI Assistant)</b></summary>
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.
</details>
<details>

<summary><b>Gemini CLI</b></summary>
Add to ~/.gemini/settings.json:

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

See Gemini CLI docs for more info.

</details>
<details>

<summary><b>Augment Code</b></summary>
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.
</details>
<details>

<summary><b>Qwen Code</b></summary>
Run this command to add Desktop Commander:

sh
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.

</details>
<details>

<summary><b>ChatGPT / Claude Web (Remote MCP)</b></summary>
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
The easiest way to completely remove Desktop Commander:

bash
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

If the automatic uninstaller doesn't work or you prefer manual removal:
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
2. 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:

  

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

Close and restart Claude Desktop to complete the removal.

Data Analysis:

"Analyze sales.csv and show top customers" → Claude runs Python code in memory

Remote Access:

"SSH to my server and check disk space" → Claude maintains SSH session

Development:

"Start Node.js and test this API" → Claude runs interactive Node session

Search/Replace Block Format:

filepath.ext
<<<<<<< SEARCH
content to find
=======
new content
>>>>>>> REPLACE

Example:

src/main.js
<<<<<<< SEARCH
console.log("old message");
=======
console.log("new message");
>>>>>>> REPLACE
```

Desktop Commander can be run in Docker containers for complete isolation from your host system, providing zero risk to your computer. This is perfect for testing, development, or when you want complete sandboxing.

1. Install Docker for Windows/Mac
- Download and install Docker Desktop from docker.com

2. Get Desktop Commander Docker Configuration
- Visit: https://hub.docker.com/mcp/server/desktop-commander/manual
- Option A: Use the provided terminal command for automated setup
- Option B: Click "Standalone" to get the config JSON and add it manually to your Claude Desktop config

3. Mount Your Machine Folders (Coming Soon)
- Instructions on how to mount your local directories into the Docker container will be provided soon
- This will allow you to work with your files while maintaining complete isolation

- Complete isolation from your host system
- Consistent environment across different machines
- Easy cleanup - just remove the container when done
- Perfect for testing new features or configurations