Pain point · Integrations · Blocks work
Supabase MCP OAuth fails in Cursor with unrecognized client_id
1 source thread · first seen 2026-03
Summary
Authenticating the official Supabase MCP server from Cursor fails and no token is returned, regardless of config or key changes.
- Affects
- Cursor users of Supabase MCP
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“The OAuth flow never completes and Cursor never receives a token”