Skip to content

Debugging

spawn uvx ENOENT: run the reference fetch server in Claude Desktop

Fix spawn uvx ENOENT for mcp-server-fetch in Claude Desktop: find the full path to uvx, put it in the config, or run the mcp/fetch Docker image, then read the log.

By Lucian Dyer, FetchMCP team · Published

This article was drafted with AI assistance from the sources listed below and edited and published by the FetchMCP team.

From spawn uvx ENOENT to a working fetch server
  1. 1Read the MCP logsConfirm the error is spawn uvx ENOENT, not a server crash.
  2. 2Run it in a terminalnpx @modelcontextprotocol/inspector uvx mcp-server-fetch. If it works there, the app cannot find uvx.
  3. 3Find the pathwhich uvx on macOS and Linux, where uvx on Windows.
  4. 4Put it in commandReplace "uvx" with the full path in claude_desktop_config.json.
  5. 5Quit and restartQuit Claude Desktop completely, start it again, check the connectors list.

You pasted the reference fetch server's snippet into Claude Desktop, restarted, and the server never connected. The log says spawn uvx ENOENT. The server is usually fine. Claude Desktop just cannot find the program you told it to start.

Checked against the fetch server README, the MCP docs and the uv docs on 2026-11-16.

What the error says

spawn uvx ENOENT means the app tried to start a process called uvx and could not find it. The reference server's README gives this entry for Claude Desktop:

{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

"command": "uvx" is a bare name, so the app has to find it on its own PATH. dbt's MCP troubleshooting page names the cause: the client cannot find uvx in its PATH because it starts with a limited environment.

That is why the same command works in your terminal. uv's standalone installer puts uv and uvx in a user executable directory: the first of $XDG_BIN_HOME, $XDG_DATA_HOME/../bin and $HOME/.local/bin on macOS and Linux (%USERPROFILE%\.local\bin on Windows when the XDG variables are unset). uv's docs describe that directory as one that should be on the PATH; the app starts with a limited environment, so it can still miss it.

1. Confirm it in the log

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log follows the MCP logs on macOS. On Linux they are in ~/.config/Claude/logs, and on Windows in %APPDATA%\Claude\logs:

type "%APPDATA%\Claude\logs\mcp*.log"

mcp.log records connections and connection failures. Each server's stderr goes to mcp-server-SERVERNAME.log. If the server never started, the spawn error is the line to find. If the server started and then printed its own error, the cause is elsewhere; work through the connection runbook.

2. Prove the server runs outside the app

npx @modelcontextprotocol/inspector uvx mcp-server-fetch starts the server under MCP Inspector, from your terminal, with your shell's PATH:

npx @modelcontextprotocol/inspector uvx mcp-server-fetch

If Inspector connects and lists the server's tools, the server and uv are fine. What is left is the app's view of PATH.

3. Put the full path in the config

which uvx prints the path on macOS and Linux. On Windows, run where uvx in Command Prompt or PowerShell.

which uvx

Replace the bare name with what it prints. dbt's example for macOS with Homebrew is /opt/homebrew/bin/uvx; with uv's standalone installer and no XDG variables set, it is $HOME/.local/bin/uvx. Write the path out in full, with your real user name:

{
  "mcpServers": {
    "fetch": {
      "command": "/Users/username/.local/bin/uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

The config lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows and ~/.config/Claude/claude_desktop_config.json on Linux. Settings, then Developer, then "Edit Config" opens it.

4. Quit completely and restart

Quit Claude Desktop fully and start it again; the app loads the config and starts its servers at launch. Then open the "Add files, connectors, and more" menu in the chat input and check that fetch appears under the connectors. For a server that still does not show up, the MCP docs list this order: restart, check the JSON syntax, use absolute paths, read the logs, run the server by hand.

Other ways to start the same server

"command": "docker" with "args": ["run", "-i", "--rm", "mcp/fetch"] is the README's Docker entry. It needs Docker on the machine.

{
  "mcpServers": {
    "fetch": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "mcp/fetch"]
    }
  }
}

pip install mcp-server-fetch is the README's third route, with "command": "python" and "args": ["-m", "mcp_server_fetch"]. Point command at the Python that has the package installed, again by full path.

"env": {"PYTHONIOENCODING": "utf-8"} is a separate fix. The README suggests it for timeouts on Windows, not for ENOENT. Add it to the server entry only if the server starts and then times out.

The transport guide explains when a local or a remote server fits.

Frequently asked questions

What does spawn uvx ENOENT mean?

Claude Desktop tried to start the command uvx and could not find it. The app starts with a limited environment, so a uvx that works in your terminal can still be missing from the app's PATH.

How do I fix spawn uvx ENOENT in Claude Desktop?

Run which uvx on macOS or Linux, or where uvx on Windows, and put the full path it prints in the command field of the server entry in claude_desktop_config.json. Then quit Claude Desktop completely and start it again.

Where are Claude Desktop's MCP logs?

In ~/Library/Logs/Claude on macOS, %APPDATA%\Claude\logs on Windows and ~/.config/Claude/logs on Linux. mcp.log covers connections and connection failures; mcp-server-SERVERNAME.log holds the stderr output of one server.

Can I run mcp-server-fetch without uvx?

Yes. The reference server's README also documents pip install mcp-server-fetch with python -m mcp_server_fetch as the command, and a Docker entry that runs docker run -i --rm mcp/fetch.

Sources

  1. Fetch MCP server README (modelcontextprotocol/servers) (Documentation)
  2. Can't find the uvx executable (dbt MCP troubleshooting) (Documentation)
  3. Connect to local MCP servers (Model Context Protocol docs) (Documentation)
  4. Storage (uv docs) (Documentation)