Supabase mcp bug - Client closed

[ai-nuke]

Could someone please help me with this? I’m using windows and v0.46. I did everything correctly as mentioned in the supabase page but it says client closed. I have added npm and npx to PATH.

[deanrie]

Hey, try this:

I can't seem to get MCP working with my Supabase

The only thing that solved it for me was running it outside as a terminal by using the command like this. cmd /c npx -y @modelcontextprotocol/server-postgres <connection-string>

[npm-error]

Here is the solution, i just had someone helping me with that:

MCP Servers on windows 10 not working? Please Help Supabase MCP Server

[supa1] [supa2] I’m having trouble getting the MCP Server for Supabase to work on my Windows 10 Pro machine. No matter what I do, it just won’t start. Here’s what I’ve tried so far: Disabled the firewall Installed a fresh version of Node.js Restarted my computer Disabled antivirus Tried a few other troubleshooting steps Despite all this, I still can’t get it running. Has anyone encountered a similar issue or have any ideas on how to fix it? Any help would be greatly appreciated!

[eug]

I solved this issue by using direct connection string from supabase (their docs suggest Session Pooler), and I added the cmd /c trick in the MCP command. The only downside is that it opens a terminal prompt while running it.

[VirtualDylan]

You are awesome, thank you! Using the direct connection string plus the following mcp.json did the trick on Win11 Pro. A blank terminal/cmd opens and I just minimize it. Doesn’t seem like it displays anything while having cursor use the MCP connection

{
  "mcpServers": {
    "supabase": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-postgres", "<direct conn string>"]
    }
  }
}