Cannot get it to run on roo code

[prathyooshan]

Bug report

Describe the bug

Tried running this on roo code and got the following error:

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]: 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. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn cleanup Failed to remove some dire...(error message truncated)

[gregnr]

Hey @prathyooshan, thanks for reporting. This error message alone doesn't give us too much information to debug with. Could you please provide:

• Your OS version
• Steps you took to set the MCP server up in Roo Code
• Where the error message was displayed when you saw it

Thanks!

[gregnr]

Following up to this, I've seen a few others with a similar message and the underlying cause appears to be related to either:

• Using an old version of Node.js (<22)
• Having multiple installations of Node.js (eg. both direct download and via nvm at the same time)

Do either of these apply to you?

[benaduggan]

I'm having the same issue. I'm on mac using Node 20 which is still definitely the default for most people. Not everything is supported on Node 22 yet.

[Joooost]

Same here but using Cline:

Windows 11 Pro
Node: 23.11.0
NPM: 10.9.2

One install with winget install nodejs

Other MCP servers such as filesystem are working for the record

[andrewhopper]

Same thing here:

2025-04-05T19:23:23.770Z [supabase] [info] Initializing server...
2025-04-05T19:23:23.778Z [supabase] [info] Server started and connected successfully
2025-04-05T19:23:23.778Z [supabase] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
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.
2025-04-05T19:23:31.909Z [supabase] [info] Server transport closed
2025-04-05T19:23:31.909Z [supabase] [info] Client transport closed
2025-04-05T19:23:31.909Z [supabase] [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-04-05T19:23:31.910Z [supabase] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"}
2025-04-05T19:23:31.910Z [supabase] [info] Client transport closed

[andrebalza]

Adding the -q (quiet) flag does solve this issue.
Sample mcp.json:

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "-q",
        "@supabase/mcp-server-supabase@latest",
        "--access-token",
        "your_token_here"
      ]
    }
  }
}

[nickvarterian]

Adding the -q (quiet) flag does solve this issue. Sample mcp.json:

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "-q",
        "@supabase/mcp-server-supabase@latest",
        "--access-token",
        "your_token_here"
      ]
    }
  }
}

This still doesn't seem to work for me. I tried Node 22.14 & 23.11 while making sure only one is installed. Restarted mcp client and computer. even when I run the npx cmd outside of the mcp client in the cmd line I am still getting warning with -q. Any Tips?