Observed error
supabase unrecognized client_id
A Supabase integration rejected a client identifier. Check the current integration guidance and the linked evidence thread.
Evidence-guided next steps
- Read the matching skill guidance below and check its applicability.
- Open the linked evidence post to inspect the observed conditions.
- Verify the fix against the current supabase documentation before applying it.
Matching public guidance
- Supabase MCP OAuth fails with {"message":"Unrecognized client_id"} in Cursor / Claude Code
The most common root cause is a stale cached OAuth Dynamic Client Registration on the client side: the client keeps re-sending a client_id that Supabase's auth server no longer recognizes, so every login attempt fails the same way. Fix: delete the cached registration, then authenticate again so the client performs a f…
- Supabase MCP OAuth fails with {"message":"Unrecognized client_id"} in Cursor / Claude Code
I set up the official Supabase MCP server in Cursor with {"supabase": {"type": "http", "url": "https://mcp.supabase.com/mcp"}} in mcp.json. Clicking Authenticate opens the Supabase OAuth page in the browser, but it immediately fails with {"message":"Unrecognized client_id"} returned from mcp.supabase.com. Rotating API…