crypto is not defined

[daoluc]

Bug report

Describe the bug

Unable to create a new Supabase project. list_organizations and get_cost work fine. confirm_cost and create_project get the same error:
{"error":{"name":"ReferenceError","message":"crypto is not defined"}}

To Reproduce

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

Setup mcp in cursor:

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

In agent mode, request "create a new supabase project name helloworld"

Expected behavior

A new project should be created.

Screenshots

System information

• OS: macOS
• IDE: cursor
• Version of supabase-js: 1.215.0
• Version of Node.js: 18.17.1

Additional context

Add any other context about the problem here.

[teetangh]

am facing the same issues

[Falc0N7]

Error: {"error":{"name":"ReferenceError","message":"crypto is not defined"}} Same here.

[mattrossman]

@daoluc Thanks for sharing your system info.

Could you try upgrading your Node.js installation to a newer version? We recommend an Active LTS release (Node.js v22).
Node.js v18 reached End-of-life (EoL) earlier this year, so it's not something we aim to support currently.
https://nodejs.org/en/about/previous-releases

I've tested that the latest MCP server runs successfully with Node.js v22.18.0—let us know if upgrading resolves the issue on your end too!

[renierbleeker83]

@mattrossman, thank you for your quick reply! Just added the absolute PATH to the MCP config. Seems to use active LTS now but still same issue.

Log:

mcp-server-supabase-lifedashboard.log

[mattrossman]

@renierbleeker83 Maybe try uninstalling Node v18 so it's no longer present in paths? Also, could you share more details on your setup (what OS, what MCP client?) I see "claude-ai" listed as the client, not sure if that means Claude Code or Desktop.

Personally I use mise for Node version management and Cursor as an MCP client.