Desktop Commander Installation Victory Guide

📖 The Journey Overview

This guide documents the successful installation of Desktop Commander MCP for Claude Desktop on Windows 11, including all the challenges we faced and how we overcame them. This real-world troubleshooting session reveals important insights for anyone attempting this installation.

What We Built

✅ Desktop Commander MCP Server (full terminal control)
✅ SLOS Memory System (Docker containers: Redis, ChromaDB, API)
✅ Full filesystem access across C:\ drive
✅ Windows automation capabilities

⚠️ Critical Pitfalls We Discovered

Wrong Docker Image Names

We initially tried several incorrect Docker image names:

❌ ghcr.io/wonderwhy-er/desktop-commander:latest
❌ wonderwhy-er/desktop-commander:latest
✅ mcp/desktop-commander:latest (correct but still didn't work)

Lesson: The Docker approach wasn't working at all on Windows!

Docker Desktop Blocking Issues

Multiple Docker Desktop processes were preventing startup (PIDs: 21680, 34788, 35108). We had to manually stop these processes through Docker Desktop's error dialog.

Claude Config File Conflicts

Multiple MCP server entries in the config file caused connection errors. We had to clean the config to only include Desktop Commander.

PowerShell Tool Failures

The Windows-MCP PowerShell tool would timeout or fail silently, especially with NPX commands. We had to work around this with batch files.

🎯 The Winning Strategy

The breakthrough came when we abandoned the Docker approach and used NPX directly with Node.js. The key was using the correct NPM package: @wonderwhy-er/desktop-commander

The Winning Installation Timeline

Multiple Docker Attempts Failed

Tried various Docker image names, all failed silently or didn't exist

Docker Desktop Process Conflicts

Had to manually stop conflicting processes through Docker Desktop

Discovered NPM Package Exists

Found @wonderwhy-er/desktop-commander through web search

Ran NPX Setup Command

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

Installation Succeeded!

Desktop Commander added to Claude's configuration

✅ Step-by-Step Installation Guide

Prerequisites

Install Node.js
Download from nodejs.org (LTS version recommended)
This provides NPM and NPX which are essential
Ensure Docker Desktop is Running
Start Docker Desktop and wait for it to fully initialize
Check for and resolve any startup conflicts
Have Claude Desktop Installed
Download from claude.ai/download

Installation Process

Open Terminal/PowerShell
Run as Administrator for best results
Run the NPX Setup Command
```
npx -y @wonderwhy-er/desktop-commander@latest setup
```
The -y flag auto-accepts the package installation
Wait for Success Message
You should see: "Desktop Commander MCP vunknown successfully added to Claude's configuration"
Restart Claude Desktop
Close Claude completely (check system tray)
Start Claude again
Verify Installation
Ask Claude to run: desktop-commander:get_config
If successful, you'll see the configuration JSON

🔧 Troubleshooting Guide

If You See "Could not attach to MCP server" Errors

Solution: Clean your config file to only include Desktop Commander:

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

Location: %APPDATA%\Claude\claude_desktop_config.json

If PowerShell Commands Timeout

Solution: Create a batch file to run commands manually:

@echo off
npx -y @wonderwhy-er/desktop-commander@latest setup
pause

Save as install-desktop-commander.bat and run it

If Docker Desktop Won't Start

Solution: Look for the error dialog showing conflicting processes. Click "Stop processes" to clean up stuck Docker instances.

🎓 Key Lessons for Teaching

What Worked

✅ Using NPX with the exact package name: @wonderwhy-er/desktop-commander
✅ Web searching for the actual NPM package to verify it exists
✅ Creating batch files as workarounds when PowerShell tools fail
✅ Cleaning the config file to eliminate conflicts
✅ Being persistent and trying multiple approaches

Teaching Tip: Always verify package names exist before attempting installation. Use npm search or check npmjs.com directly!

Teaching Tip: When documentation mentions multiple installation methods, try the NPX method first on Windows - it's usually the most reliable!

🚀 Final Configuration

What You Get With Desktop Commander

{
  "version": "0.2.14",
  "capabilities": [
    "Full terminal command execution",
    "Advanced file editing with fuzzy search",
    "Process management and monitoring",
    "System configuration control",
    "Persistent work environment",
    "Automatic updates on Claude restart"
  ],
  "restrictions": [
    "Dangerous system commands blocked",
    "Safety measures in place"
  ]
}

Your Complete Stack

SLOS-METAMIND Architecture Components

🧠 Desktop Commander: System control and automation
💾 Redis Container: Fast key-value state storage
🔍 ChromaDB Container: Semantic pattern storage
🌉 FastAPI Bridge: Connection layer on port 8080
📁 Filesystem Access: Full C:\ drive access

📚 Resources and References

Desktop Commander GitHub: github.com/wonderwhy-er/DesktopCommanderMCP
NPM Package: npmjs.com/package/@wonderwhy-er/desktop-commander
Claude Desktop Download: claude.ai/download
Node.js Download: nodejs.org

Config File Locations

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

🚀 Desktop Commander Installation Victory Guide