Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: spawn uvx ENOENT when using "fetch" server #760

Open
oliverangelil opened this issue Mar 8, 2025 · 0 comments
Open

Error: spawn uvx ENOENT when using "fetch" server #760

oliverangelil opened this issue Mar 8, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@oliverangelil
Copy link

Describe the bug
Trying the fetch server on a mac. Have uvx v0.6.5 installed in the terminal, and it works in the teminal.
which uvx returns:
/Users/oliverangelil/.local/bin/uvx

Getting this error when restarting Claude Desktop:
Error: spawn uvx ENOENT

To Reproduce
My config.json file looks like:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/oliverangelil/Desktop",
        "/Users/oliverangelil/Downloads"
      ]
    },
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

Logs

2025-03-08T07:34:14.431Z [fetch] [info] Initializing server...
2025-03-08T07:34:14.442Z [fetch] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-08T07:34:14.443Z [fetch] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-08T07:34:14.448Z [fetch] [info] Server transport closed
2025-03-08T07:34:14.448Z [fetch] [info] Client transport closed
2025-03-08T07:34:14.449Z [fetch] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...') in JavaScript, print('...', file=sys.stderr) in python) and it will appear in this log.
2025-03-08T07:34:14.449Z [fetch] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
2025-03-08T07:34:15.286Z [fetch] [info] Initializing server...
2025-03-08T07:34:15.292Z [fetch] [error] spawn uvx ENOENT {"context":"connection","stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-08T07:34:15.292Z [fetch] [error] spawn uvx ENOENT {"stack":"Error: spawn uvx ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-03-08T07:34:15.293Z [fetch] [info] Server transport closed
2025-03-08T07:34:15.293Z [fetch] [info] Client transport closed
2025-03-08T07:34:15.293Z [fetch] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...') in JavaScript, print('...', file=sys.stderr) in python) and it will appear in this log.
2025-03-08T07:34:15.293Z [fetch] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}

@oliverangelil oliverangelil added the bug Something isn't working label Mar 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant