Supabase MCP persistent "crypto is not defined" error

[gokulsrin]

So, basically, my MCP was working wonderfully until today, when I was trying to use to find some items for me in my DB, when I started getting these persistent "crypto not defined" errors whenever using the execute_sql tool. Here is an example:

Can you run the supabase mcp and read one table. Forget boot seq

⏺ I'll run the Supabase MCP and read a table for you. Let me first list the available projects to get the project ID.
⎿ [
{
"id": "XXXXXXX",
… +13 lines (ctrl+r to expand)

⏺ Now let me list the tables in this project:

⏺ supabase - list_tables (MCP)(project_id: "XXXXXXX")
⎿ ⚠ Large MCP response (~21.2k tokens), this can fill up context quickly
⎿ [
{
"schema": "public",
… +5813 lines (ctrl+r to expand)

⏺ Let me read the first 10 rows from the notes table to show you the structure:

⏺ supabase - execute_sql (MCP)(project_id: "XXXXXXX", query: "SELECT x, y, z, z, z \nFROM z \nLIMIT 10")
⎿ Error: {"error":{"name":"ReferenceError","message":"crypto is not defined"}}

Historically, these commands would work with no issue. But now, suddenly, they don't. I'm using claude code and running node v18.20.5.

[sadafsajju]

same issue here 'Error: {"error":{"name":"ReferenceError","message":"crypto is not defined"}}'

[gokulsrin]

Wait, the problem was the node version. Just upgrade to > 20. This resolved that above mentioned issue for me!

[gokulsrin]

Wait, the problem was the node version. Just upgrade to > 20. This resolved that above mentioned issue for me!

[gichigi]

I could kiss you

thanks bro

[prtksage]

Wait, the problem was the node version. Just upgrade to > 20. This resolved that above mentioned issue for me!

thanks bud,

[ls-ynevet]

I’m on v22.9.0 and still encountering this error. Could this be an internal bug in your MCP server?

[vahidkowsari]

V22 worked for me.
I did this
nvm install v22
nvm alias default v22
rm -rf ~/.npm/_npx
npm cache clean --force
And restart your ide (windsurf in my case)

[Joro-Popov]

I am also facing the same issue. I am using node version 22.14 and it used to work few days ago. I tried @vahidkowsari 's solution, but didn't work for me