The Independent PC · Module 2 · Tool Setup

Fix Your MCP Servers

Claude Desktop can't find npx · Windows path-spaces bug · 5-minute fix

The Error

You open Claude Desktop. Your MCP tools show as disconnected. The log says:

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
...
[filesystem] [error] Server disconnected.

Your filesystem, memory, puppeteer, and fetch servers all fail to start.

Diagnosis

This is a Windows path-spaces bug. When Claude Desktop resolves npx to its full path, it expands to:

C:\Program Files\nodejs\npx.cmd   ← space in path, unquoted

Windows splits the command at the space and tries to execute C:\Program as the executable. It fails immediately. Your config is fine — Claude Desktop's path resolver is the problem.

This is exactly the kind of invisible friction I built this course around. You did nothing wrong. The tool has a bug. Windows has had this exact problem since the 1990s. Knowing it exists — and knowing the workaround — is the difference between someone who controls their machine and someone who gives up and thinks "AI tools don't work."

The Fix

Replace every "command": "npx" entry with the Windows 8.3 short path — a space-free alias that Windows has supported since forever:

⚡

C:\PROGRA~1\nodejs\npx.cmd is the short-path equivalent of C:\Program Files\nodejs\npx.cmd. No spaces. No quoting problem. Always works.

Open this file and replace its entire contents:

C:\Users\[YOU]\AppData\Roaming\Claude\claude_desktop_config.json 
{
  "mcpServers": {
    "filesystem": {
      "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "C:\\Users\\fkurk\\Documents",
        "C:\\Users\\fkurk\\Desktop",
        "G:\\My Drive",
        "G:\\My Drive\\TQL"
      ]
    },
    "memory": {
      "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ]
    },
    "brave-search": {
      "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
      "args": [
        "-y",
        "@modelcontextprotocol/server-brave-search"
      ],
      "env": {
        "BRAVE_API_KEY": "YOUR_BRAVE_API_KEY"
      }
    },
    "fetch": {
      "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch"
      ]
    },
    "puppeteer": {
      "command": "C:\\PROGRA~1\\nodejs\\npx.cmd",
      "args": [
        "-y",
        "@modelcontextprotocol/server-puppeteer"
      ]
    }
  },
  "preferences": {
    "coworkWebSearchEnabled": true,
    "coworkScheduledTasksEnabled": true,
    "ccdScheduledTasksEnabled": true,
    "sidebarMode": "chat"
  }
}
Deploy It
  1. Press Win + R, type %APPDATA%\Claude, hit Enter
  2. Open claude_desktop_config.json in Notepad or VS Code
  3. Select all → paste the config above (update your username and Brave API key)
  4. Save the file
  5. Find Claude in the system tray → right-click → Quit (don't just close the window)
  6. Relaunch Claude Desktop — your MCP servers should show green
Verify

Once Claude restarts, test with a simple prompt:

// Type this in Claude Desktop chat:

List the files in my Documents folder.

If Claude returns a file listing, your filesystem MCP is working. If you see an error, check that your username in the paths matches your actual Windows username.

Want more like this?

I write about AI, Windows, and taking control of your computing environment. Free lessons, tools, and guides — built for people who want to actually understand what's happening inside their machines.

Subscribe on Substack →
Substack · About Frank · Talk to the Book · Email Frank
© 2026 Frank Kurka · The Independent PC Module 2 · Setup