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

cant connect to windusrf #16

Open
adiel098 opened this issue Apr 2, 2025 · 6 comments
Open

cant connect to windusrf #16

adiel098 opened this issue Apr 2, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@adiel098
Copy link

adiel098 commented Apr 2, 2025

i set it by your guide
{
"mcpServers": {
"supabase": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@supabase/mcp-server-supabase@latest",
"--access-token",
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
]
}
}
}

and also download the libary but still not working and getting this error in output:

[Error - 12:05:41 PM] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 12:05:41 PM] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099

@adiel098 adiel098 added the bug Something isn't working label Apr 2, 2025
@gregnr
Copy link
Collaborator

gregnr commented Apr 2, 2025

Hey @adiel098 thanks for reporting. On Windows this has been known to happen if node/npx isn't available in your system PATH environment variable. Can you confirm it is available there, and also which version of node you are running?

@adiel098
Copy link
Author

adiel098 commented Apr 3, 2025

[Error - 11:40:12 AM] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 11:40:12 AM] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099

i tried again now and still have the probelm
node v18.18.0

@gregnr
Copy link
Collaborator

gregnr commented Apr 3, 2025

Can you please try:

  • Upgrading to the latest LTS node version
  • Restart your computer

If neither of these work, a good way to debug is to use the MCP inspector:

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

Then while that runs, go to http://127.0.0.1:6274/ and hit "Connect".

@rerouted
Copy link

rerouted commented Apr 4, 2025

I am having the same problem in Windsurf. The state of the server is reporting as "request failed". I ran the MCP Inspector and get a lot of deprecated warnings as well.

npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.

@crsmoore
Copy link

crsmoore commented Apr 4, 2025

Having the same problem on Windsurf.

Latest version of macOS, latest version of Windsurf.

Have node installed.

Doesn't work.

Image

Image

@crsmoore
Copy link

crsmoore commented Apr 4, 2025

It also connects for a bit in Cursor, but then fails out.

Image

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

4 participants