Bug report

Describe the bug

Every time I try to use the supabase MCP it always says client closed

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Go to '…'
Click on '…'
Scroll down to '…'
See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

OS: macOS

Additional context

Add any other context about the problem here.

Apr 05 '25 14:04 phoenix-error

i have this same issue

Apr 05 '25 15:04 jacobabiola

Same issue: 2025-04-05 09:29:11.125 [info] base: Client closed for command 2025-04-05 09:29:11.126 [error] base: Error in MCP: Client closed 2025-04-05 09:29:11.132 [info] base: Handling ListOfferings action 2025-04-05 09:29:11.132 [error] base: No server info found

On windows

Apr 05 '25 16:04 thatguyrynodyno

Same here

On macbook

Apr 05 '25 17:04 niclastanskanen

Same issue here

Apr 05 '25 21:04 conticomp

Same problem here. Also doesn't work in Windsurf.

Apr 06 '25 03:04 crsmoore

Yes , same issue for me too.

Apr 06 '25 09:04 growthriseagency

same here on mac

Apr 06 '25 20:04 radzio

Same here

Apr 07 '25 10:04 rajinsyed

same here

Apr 07 '25 11:04 Gadi-Chait

same here.

2025-04-07 16:44:24.976 [info] cial: Handling ReloadClient action 2025-04-07 16:44:24.976 [info] cial: getOrCreateClient for stdio server. process.platform: darwin isElectron: true 2025-04-07 16:44:24.976 [info] cial: Starting new stdio process with command: npx -y @supabase/mcp-server-supabase@latest --access-token sbp_XXXX8ab49e0e0df54b28ed08868db20ba65a0XXX 2025-04-07 16:44:26.659 [info] cial: Client closed for command 2025-04-07 16:44:26.659 [error] cial: Error in MCP: Client closed 2025-04-07 16:44:26.659 [error] cial: Failed to reload client: MCP error -32000: Connection closed 2025-04-07 16:44:26.660 [info] Tool: Handling ListOfferings action 2025-04-07 16:44:26.660 [info] Tool: Listing offerings 2025-04-07 16:44:26.660 [info] Tool: getOrCreateClient for stdio server. process.platform: darwin isElectron: true 2025-04-07 16:44:26.660 [info] Tool: Reusing existing stdio client 2025-04-07 16:44:26.660 [info] Tool: Connected to stdio server, fetching offerings 2025-04-07 16:44:26.664 [info] listOfferings: Found 7 tools 2025-04-07 16:44:26.664 [info] Tool: Found 7 tools, 0 resources, and 0 resource templates 2025-04-07 16:44:26.665 [info] rawl: Handling ListOfferings action 2025-04-07 16:44:26.665 [error] rawl: No server info found 2025-04-07 16:44:26.668 [info] -mcp: Handling ListOfferings action 2025-04-07 16:44:26.668 [error] -mcp: No server info found 2025-04-07 16:44:26.669 [info] cial: Handling ListOfferings action 2025-04-07 16:44:26.669 [error] cial: No server info found 2025-04-07 16:44:26.670 [info] gres: Handling ListOfferings action 2025-04-07 16:44:26.670 [info] gres: Listing offerings 2025-04-07 16:44:26.670 [info] gres: getOrCreateClient for stdio server. process.platform: darwin isElectron: true 2025-04-07 16:44:26.670 [info] gres: Reusing existing stdio client 2025-04-07 16:44:26.670 [info] gres: Connected to stdio server, fetching offerings 2025-04-07 16:44:26.672 [info] listOfferings: Found 1 tools 2025-04-07 16:44:26.672 [info] gres: Found 1 tools, 0 resources, and 0 resource templates 2025-04-07 16:44:27.218 [error] -mcp: Client error for command SSE error: TypeError: fetch failed: connect ECONNREFUSED 127.0.0.1:3333, connect ECONNREFUSED ::1:3333 2025-04-07 16:44:27.218 [error] -mcp: Error in MCP: SSE error: TypeError: fetch failed: connect ECONNREFUSED 127.0.0.1:3333, connect ECONNREFUSED ::1:3333 2025-04-07 16:44:30.227 [error] -mcp: Client error for command SSE error: TypeError: fetch failed: connect ECONNREFUSED 127.0.0.1:3333, connect ECONNREFUSED ::1:3333 2025-04-07 16:44:30.228 [error] -mcp: Error in MCP: SSE error: TypeError: fetch failed: connect ECONNREFUSED 127.0.0.1:3333, connect ECONNREFUSED ::1:3333 2025-04-07 16:44:33.233 [error] -mcp: Client error for command SSE error: TypeError: fetch failed: connect ECONNREFUSED 127.0.0.1:3333, connect ECONNREFUSED ::1:3333 2025-04-07 16:44:33.233 [error] -mcp: Error in MCP: SSE error: TypeError: fetch failed: connect ECONNREFUSED 127.0.0.1:3333, connect ECONNREFUSED ::1:3333

Apr 07 '25 14:04 feelfetch

same issue on Linux

Apr 07 '25 17:04 fls-pax

Same issue on Mac with cursor and windsurf. Tried multiple versions of node and mcp with no resolution.

Apr 08 '25 02:04 maycoth

Same here with Claude on Windows (both with the Claude app and via Cline + VS Code).

Apr 08 '25 20:04 ApeOnFire

Same here on Mac with Cursor

Apr 10 '25 09:04 ghidoz

Same for me on MacBook with Cursor

Apr 10 '25 09:04 mohammedsagban

Using @supabase/mcp-server-supabase instead of @supabase/mcp-server-supabase@latest solved it for me

Apr 14 '25 18:04 aproli90

Using @supabase/mcp-server-supabase instead of @supabase/mcp-server-supabase@latest solved it for me

this worked for me .. Legend

Apr 14 '25 19:04 jacobabiola

@aproli90 and @jacobabiola glad you solved this though this is concerning that @latest fails. Can you confirm that you include a -y in front? ie:

npx -y @supabase/mcp-server-supabase@latest --access-token=<personal-access-token>

Edit: Another good step to debug is checking the version - what does this command give you?

npx -y @supabase/mcp-server-supabase@latest --version

Apr 14 '25 19:04 gregnr

@aproli90 and @jacobabiola glad you solved this though this is concerning that @latest fails. Can you confirm that you include a -y in front? ie:

npx -y @supabase/mcp-server-supabase@latest --access-token= Edit: Another good step to debug is checking the version - what does this command give you?

npx -y @supabase/mcp-server-supabase@latest --version

Yes it includes -y in front.

Apr 14 '25 19:04 jacobabiola

Strange that -y didn't work with @latest - I'll keep digging into this.

Just a heads up - you leaked your access token in that screenshot - be sure to rotate it!

Apr 14 '25 19:04 gregnr

Strange that -y didn't work with @latest - I'll keep digging into this.

Just a heads up - you leaked your access token in that screenshot - be sure to rotate it!

yes i rotated it. Thank you for letting me know though.

Apr 14 '25 19:04 jacobabiola

I have had the same issue on windows for a while and have noticed if you manually change it from @supabase/mcp-server-supabase@latest to @supabase/[email protected] it fixes the issue.

Apr 14 '25 20:04 ApplaudedTwo7

@ApplaudedTwo7 what version of node and npx are you running? I wonder if this is affecting this.

node --version
npx --version

I've tried reproducing on macOS and Windows and both work with @latest on the following versions:

macOS:

node --version
v22.9.0
npx --version
10.8.3

Windows:

node --version
v22.14.0
npx --version
10.9.2

Apr 14 '25 21:04 gregnr

@aproli90 and @jacobabiola glad you solved this though this is concerning that @latest fails. Can you confirm that you include a -y in front? ie:

npx -y @supabase/mcp-server-supabase@latest --access-token=

Edit: Another good step to debug is checking the version - what does this command give you?

npx -y @supabase/mcp-server-supabase@latest --version

I get error when trying to find the version of @latest