How to Fix Silent MCP Server Failures in Claude Desktop (spawn ENOENT, uvx not found, Windows paths)

1. spawn ENOENT — server never starts

Symptom: No tools icon. MCP logs say spawn ENOENT or Error: spawn npx ENOENT.

Why it happens: Claude Desktop spawns MCP servers as child processes using a minimal shell environment. It does not inherit the PATH your terminal sees. Any command installed via Homebrew, nvm, pyenv, asdf, or a user-level package manager is invisible from inside Claude Desktop.

Fix — use the absolute path in the command field:

// Find the path first:
which npx     # macOS / Linux
where npx     # Windows PowerShell

// Then use it in your config:
{
  "mcpServers": {
    "filesystem": {
      "command": "/usr/local/bin/npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects"]
    }
  }
}

For uvx:

which uvx
# typically one of:
#   /home/you/.local/bin/uvx   (Linux)
#   /opt/homebrew/bin/uvx      (macOS via Homebrew)

2. uvx not found — uv is not installed

Symptom: Servers using uvx (git, sqlite, sentry, time, fetch, redis) never start. Logs show uvx: command not found or spawn uvx ENOENT.

Why it happens: uvx ships as part of the uv package manager, which is separate from pip or Python itself. If you have not installed uv, every server that uses uvx will silently fail.

Fix — install uv:

# macOS / Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# Windows (PowerShell)
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

After installing, restart your terminal, run which uvx, and add that absolute path to your config. Then restart Claude Desktop.

3. npx vs uvx — using the wrong runtime

Symptom: The command is there but the server never starts. The log shows a package-not-found error, or the wrong package manager tries to install a package it cannot find.

Why it happens: MCP servers are distributed through two separate ecosystems. npm servers need npx. Python/uv servers need uvx. Using the wrong one silently fails.

Quick rule: if the package name starts with @modelcontextprotocol/server- and is on npm, use npx. If it starts with mcp-server- and is on PyPI, use uvx.

// npx server (npm):
{
  "github": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-github"],
    "env": {"GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."}
  }
}

// uvx server (Python/uv):
{
  "git": {
    "command": "uvx",
    "args": ["mcp-server-git", "--repository", "/home/you/myrepo"]
  }
}

4. Windows path escaping

Symptom: On Windows, filesystem, git, or SQLite server starts but errors on any path operation. Or servers fail to start at all because the config is invalid.

Why it happens: JSON requires backslashes to be escaped as \\, but many MCP servers also parse Windows-style paths unreliably. A single unescaped backslash silently invalidates your entire config file.

Fix — use forward slashes everywhere on Windows:

{
  "mcpServers": {
    "filesystem": {
      "command": "C:/Users/you/AppData/Roaming/npm/npx.cmd",
      "args": ["-y", "@modelcontextprotocol/server-filesystem",
               "C:/Users/you/projects"]
    }
  }
}

Validate your JSON before restarting Claude Desktop — one bad comma or backslash silently disables all servers:

# PowerShell
Get-Content "$env:APPDATA\Claude\claude_desktop_config.json" | ConvertFrom-Json

If that throws an error, your JSON is invalid. Fix it before restarting.

5. Config not loading — no tools icon at all

You edited the config, restarted Claude Desktop, and the hammer icon (tools) never appears. Five causes in order of likelihood:

5a. Wrong file location

The config must be at the exact OS-specific path. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json — Windows: %APPDATA%\Claude\claude_desktop_config.json — Linux: ~/.config/Claude/claude_desktop_config.json.

Open it directly to confirm you are editing the right file:
macOS: open ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows: notepad "$env:APPDATA\Claude\claude_desktop_config.json"

5b. JSON syntax error

A trailing comma, a missing brace, or an unescaped character silently disables every server. Validate at jsonlint.com or with the PowerShell command above.

5c. Did not fully quit Claude Desktop

On macOS, Cmd+W closes the window but leaves the process running. Use Cmd+Q, or right-click the Dock icon and choose Quit. On Windows, right-click the system tray icon and choose Quit.

5d. Incorrect JSON structure

Servers must be nested inside "mcpServers" at the top level:

{
  "mcpServers": {
    "server-name": {
      "command": "...",
      "args": []
    }
  }
}

5e. Empty or placeholder env var

If a server requires an API key and the value is an empty string "" or a literal like "your-token-here", the server starts and immediately crashes with no visible error in the UI. Either fill in a real value or remove the env block entirely if you are not using that server yet. The free auditor catches these automatically.

6. Tools appear but every call fails or returns empty

Symptom: The tools icon is there. Claude acknowledges the tool. But every call returns empty, times out, or gives a generic error.

The server started successfully but is failing at runtime. The first step is always to read the log file for that server (see below). Common runtime causes:

How to read the MCP server logs

Most developers skip this step. Each MCP server gets its own log file and the errors there are almost always more specific than anything Claude shows in the chat UI.

# macOS
ls ~/Library/Logs/Claude/
tail -50 ~/Library/Logs/Claude/mcp-server-filesystem.log

# Windows (PowerShell)
ls "$env:APPDATA\Claude\logs\"
Get-Content "$env:APPDATA\Claude\logs\mcp-server-filesystem.log" -Tail 50

# Linux
ls ~/.config/Claude/logs/
tail -50 ~/.config/Claude/logs/mcp-server-filesystem.log

Look for: Python tracebacks, lines containing Error:, ENOENT, EACCES, ModuleNotFoundError, or HTTP 401/403 responses.

Catch all of these in one command

pip install mcp-config-lint
mcp-config-lint

FAQ