trobuleshoot ENOENT

[maketeamake]

Hi guys, previously i used official mcp postgres but decided to us your solution with unrestricted access.

I installed to Ubutntu via SSH, I am using cursor

added server like this:

{
  "mcpServers": {
    "postgres": {
      "command": "uv",
      "args": [
        "run",
        "postgres-mcp",
        "--access-mode=unrestricted"
      ],
      "env": {
        "DATABASE_URI": "postgresql://AAA:BBB@localhost:5432/rag_system"
      }
    }
  }
}

yes it did not worked with error below.

2025-04-22 14:30:46.791 [info] gres: Handling CreateClient action
2025-04-22 14:30:46.791 [info] gres: Starting new stdio process with command: uv run postgres-mcp --access-mode=unrestricted
2025-04-22 14:30:46.807 [info] gres: Handling CreateClient action
2025-04-22 14:30:46.807 [info] gres: Starting new stdio process with command: uv run postgres-mcp --access-mode=unrestricted
2025-04-22 14:30:46.814 [error] gres: Client error for command spawn uv ENOENT
2025-04-22 14:30:46.814 [error] gres: Error in MCP: spawn uv ENOENT
2025-04-22 14:30:46.815 [info] gres: Client closed for command
2025-04-22 14:30:46.815 [error] gres: Error in MCP: Client closed
2025-04-22 14:30:46.824 [info] gres: Handling ListOfferings action
2025-04-22 14:30:46.824 [error] gres: No server info found
2025-04-22 14:30:46.832 [error] gres: Client error for command spawn uv ENOENT
2025-04-22 14:30:46.832 [error] gres: Error in MCP: spawn uv ENOENT
2025-04-22 14:30:46.832 [info] gres: Client closed for command
2025-04-22 14:30:46.832 [error] gres: Error in MCP: Client closed
2025-04-22 14:30:46.842 [info] gres: Handling ListOfferings action

##Troubleshooting:

1. this is working fine for me:

root@Ubuntu-2404-noble-amd64-base ~/rag # uv run postgres-mcp postgresql://AAA:BBB@localhost:5432/rag_system
[04/22/25 13:26:47] INFO     Starting PostgreSQL MCP Server in UNRESTRICTED mode                      server.py:537
                    INFO     Successfully connected to database and initialized connection pool   

2. I also tried non-uv version with almost same error

3. GPT suggested to update absolute uv path
   "command": "/usr/local/bin/uv",

and also even create a wrapper

#!/bin/bash
source /path/to/your/virtualenv/bin/activate
exec uv "$@"

but both solutions did not worked

user and password and IP is working fine ( I tried localhost and real IP too)

cursor suggested to check extra debug from console, here is below

[rahulcap]

I've seen this before depending on how uv is installed (system vs user). Can you confirm where uv is installed with which uv? Then put that full path into the mcp json config? And then completely quit and restart the client?

Also which client are you using? It sounds like Cursor?

[maketeamake]

I've seen this before depending on how uv is installed (system vs user). Can you confirm where uv is installed with which uv? Then put that full path into the mcp json config? And then completely quit and restart the client?

Also which client are you using? It sounds like Cursor?

uv is at '/root/.local/bin/uv'
I am using cursor, yeah

tried to repalce config for this, problem persists:

{
  "mcpServers": {
    "postgres": {
      "command": "/root/.local/bin/uv",
      "args": [
        "run",
        "postgres-mcp",
        "--access-mode=unrestricted"
      ],
      "env": {
        "DATABASE_URI": "postgresql://AAA:BBB@localhost:5432/rag_system"
      }
    }
  }
}

output shows this:
2025-04-22 23:26:30.054 [info] gres: Handling ReloadClient action
2025-04-22 23:26:30.054 [info] gres: Starting new stdio process with command: /root/.local/bin/uv run postgres-mcp --access-mode=unrestricted
2025-04-22 23:26:30.080 [error] gres: Client error for command spawn /root/.local/bin/uv ENOENT
2025-04-22 23:26:30.080 [error] gres: Error in MCP: spawn /root/.local/bin/uv ENOENT
2025-04-22 23:26:30.081 [info] gres: Client closed for command
2025-04-22 23:26:30.081 [error] gres: Error in MCP: Client closed
2025-04-22 23:26:30.081 [error] gres: Failed to reload client: MCP error -32000: Connection closed
2025-04-22 23:26:30.082 [info] gres: Handling ListOfferings action
2025-04-22 23:26:30.082 [error] gres: No server info found

[jssmith]

@maketeamake I'd like to confirm a few facts about your environment:

1/ You mentioned you are running using Ubuntu via ssh. Are you using Remote SSH with Cursor or are you running Cursor on the Ubuntu machine directly?
2/ Did you run uv pip install postgres-mcp or did you install from the source code?

[maketeamake]

@maketeamake I'd like to confirm a few facts about your environment:

1/ You mentioned you are running using Ubuntu via ssh. Are you using Remote SSH with Cursor or are you running Cursor on the Ubuntu machine directly? 2/ Did you run uv pip install postgres-mcp or did you install from the source code?

So I am running windows + Cursor. Cursor is connected to SSH to Ubuntu server, with keys.

2. I installed it with two options:

pipx install postgres-mcp
(and tried pipx config, without path)

and then I tried

pipx install uv
(and tried uv config, without path and with absolute path)

now, I deleted BOTH uv and pipx
and interestingly, error is the same:

2025-04-23 11:14:57.378 [info] gres: Handling ReloadClient action
2025-04-23 11:14:57.378 [info] gres: Starting new stdio process with command: postgres-mcp --access-mode=unrestricted
2025-04-23 11:14:57.401 [error] gres: Client error for command spawn postgres-mcp ENOENT
2025-04-23 11:14:57.401 [error] gres: Error in MCP: spawn postgres-mcp ENOENT
2025-04-23 11:14:57.401 [info] gres: Client closed for command
2025-04-23 11:14:57.401 [error] gres: Error in MCP: Client closed
2025-04-23 11:14:57.402 [error] gres: Failed to reload client: MCP error -32000: Connection closed
2025-04-23 11:14:57.402 [info] gres: Handling ListOfferings action
2025-04-23 11:14:57.402 [error] gres: No server info found

so maybe problem is with this?

I also tried to install it from source code but need a bit more instructions how to add it later on to the proejct in cursor.
I tried to "mount" it with this config (after installed from source) but it was throwing same errors:

{
  "mcpServers": {
    "postgres": {
      "command": "/usr/local/bin/postgres-mcp-wrapper",
      "args": [
        "--access-mode=unrestricted"
      ],
      "env": {
        "DATABASE_URI": "postgresql://AAA:BBB@localhost:5432/rag_system"
      }
    }
  }
}

[jssmith]

This seems related to how Cursor handles MCP with remote SSH. See, e.g., this thread.

Cursor presently runs MCP servers locally, even when you are connected to the files on a remote system. It sounds like they working on a remote MCP solution but they don't have it yet.

Workaround could be: 1/ running the MCP server locally and tunneling the database connection to the Ubuntu machine, 2/ running the MCP server on the Ubuntu machine with SSE transport, then tunneling the SSE port from the local machine.

Either way, there is some additional setup involved until Cursor handles this better.

[zhangyelong]

I got the same error when trying to run postgres-mcp server locally in Cursor, I'm using Cursor Version: 0.50.4 on Macbook M2.

The workaround is to run postgres-mcp in SSE.