Issue Connecting MCP with Supabase – Project Ref Not Resolving DNS

[Hallidayo]

Original opened in supabase/supabase - Issue

Bug report

Hello Supabase Support,

I'm currently trying to integrate my Supabase project with the @supabase/mcp-server-supabase plugin for Cursor using the instructions provided in your documentation.

My setup details are as follows:

Project Ref: pasonxrplzmvdhzqmgd

System information

• OS: Windows 11
• Browser: Brave / Chrome
• Version of supabase-js: @supabase/supabase-js@2.50.0
• Version of Node.js: v22.14.0

Supabase Access Token: Generated from the [Account Settings > Access Tokens] section and defined correctly in the MCP config

Command Used:

npx -y @supabase/mcp-server-supabase@latest --read-only --project-ref=pasonxrplzmvdhzqmgd

set SUPABASE_ACCESS_TOKEN=sbp_d1302eab601b3e2a81fffdebfe2ef39760c04ffe
npx -y @supabase/mcp-server-supabase@latest --read-only --project-ref=pasonxrplzmvdhzqmgd

Despite following all instructions and seeing no apparent errors in the configuration, when trying to test or fetch schema information (e.g., SELECT * FROM companies LIMIT 3), the Cursor environment is unable to connect to the Supabase backend. It returns errors suggesting the project ref might be invalid or misconfigured.

Additionally, I attempted to curl the endpoint:

curl -H "Authorization: Bearer [TOKEN]" https://pasonxrplzmvdhzqmgd.supabase.co/rest/v1/companies?select=*

But I consistently receive the error:

Could not resolve host: pasonxrplzmvdhzqmgd.supabase.co
DNS lookups also fail (including using Google DNS), indicating that the hostname might not exist or has not propagated.

I have verified that:

The token is active and correctly copied

The project reference is correct (confirmed in the dashboard)

The MCP server does not show startup errors, but Cursor still cannot access any schema details

My Supabase project is on a free plan, and I understand MCP access should be available

I'm running this on Windows 11 with Node.js and latest npx

Could you please confirm:

Whether this project ref is active and accessible via MCP tools?

If DNS propagation or MCP feature restrictions might be causing this issue?

If there are known limitations for free-tier projects using MCP?

Any suggestions or corrections to ensure MCP can resolve and interact with my Supabase project?

Screenshots

The model is hallucinating, because when I ask for the fields of the table companies it brings me this message:

But as you can see these are the real fields of the table companies, and are not the same that cursor shows

If you require additional information just tell me.

Thank you in advance for your support.

Best regards,

Fabian Hidalgo
IT Project Manager