Supabase MCP OAuth Error #7451

Closed
opened 2026-02-16 18:07:12 -05:00 by yindo · 5 comments
Owner

Originally created by @percusser on GitHub (Jan 24, 2026).

Originally assigned to: @R44VC0RP on GitHub.

Description

I just upgraded to version 1.1.34. It said I had to reauth for the Supabase MCP server. I ran opencode mcp auth supabase and the browser window opened with this error:

{"message":"Unrecognized client_id"}

This has never happened before until just now with this latest version.

Plugins

No response

OpenCode version

1.1.34

Steps to reproduce

  1. Have supabase MCP server configured with the given config from supabase:
    { "$schema": "https://opencode.ai/config.json", "mcp": { "supabase": { "type": "remote", "url": "https://mcp.supabase.com/mcp", "enabled": true } } }

  2. run opencode mcp auth supabase

Screenshot and/or share link

No response

Operating System

macOS 26.2

Terminal

macOS terminal

Originally created by @percusser on GitHub (Jan 24, 2026). Originally assigned to: @R44VC0RP on GitHub. ### Description I just upgraded to version 1.1.34. It said I had to reauth for the Supabase MCP server. I ran `opencode mcp auth supabase` and the browser window opened with this error: `{"message":"Unrecognized client_id"}` This has never happened before until just now with this latest version. ### Plugins _No response_ ### OpenCode version 1.1.34 ### Steps to reproduce 1. Have supabase MCP server configured with the given config from supabase: `{ "$schema": "https://opencode.ai/config.json", "mcp": { "supabase": { "type": "remote", "url": "https://mcp.supabase.com/mcp", "enabled": true } } }` 2. run `opencode mcp auth supabase` ### Screenshot and/or share link _No response_ ### Operating System macOS 26.2 ### Terminal macOS terminal
yindo added the bug label 2026-02-16 18:07:12 -05:00
yindo closed this issue 2026-02-16 18:07:12 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 24, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #6842: Supabase MCP - Similar issue with Supabase MCP authentication/configuration
  • #5953: Reauthentication with Jira MCP via Oauth doesn't work - General MCP reauthentication flow issues
  • #9510: All MCP oauth flow return potential CSRF attack - Broader MCP OAuth authentication problems

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 24, 2026): This issue might be a duplicate of existing issues. Please check: - #6842: Supabase MCP - Similar issue with Supabase MCP authentication/configuration - #5953: Reauthentication with Jira MCP via Oauth doesn't work - General MCP reauthentication flow issues - #9510: All MCP oauth flow return potential CSRF attack - Broader MCP OAuth authentication problems Feel free to ignore if none of these address your specific case.
Author
Owner

@R44VC0RP commented on GitHub (Jan 24, 2026):

I wasn't able to repro this after following your steps. But upon investigation into it, this might be related to https://github.com/anomalyco/opencode/issues/6842#issuecomment-3708263422 and you might have to enable the MCP access via supabase.

https://supabase.com/docs/guides/auth/oauth-server/mcp-authentication#prerequisites

Let me know if this solves it!

@R44VC0RP commented on GitHub (Jan 24, 2026): I wasn't able to repro this after following your steps. But upon investigation into it, this might be related to https://github.com/anomalyco/opencode/issues/6842#issuecomment-3708263422 and you might have to `enable` the MCP access via supabase. https://supabase.com/docs/guides/auth/oauth-server/mcp-authentication#prerequisites Let me know if this solves it!
Author
Owner

@percusser commented on GitHub (Jan 24, 2026):

Thanks for the reply. MCP access is enabled. I am able to successfully authenticate into the Supabase MCP via OAuth in Codex and Roo Code without any OAuth errors.

@percusser commented on GitHub (Jan 24, 2026): Thanks for the reply. MCP access is enabled. I am able to successfully authenticate into the Supabase MCP via OAuth in Codex and Roo Code without any OAuth errors.
Author
Owner

@R44VC0RP commented on GitHub (Jan 24, 2026):

Can you try to repro with adding --print-logs to the end of the command?

@R44VC0RP commented on GitHub (Jan 24, 2026): Can you try to repro with adding `--print-logs` to the end of the command?
Author
Owner

@percusser commented on GitHub (Jan 24, 2026):

I figured it out! I guess opencode doesn't like when there are MCP servers with the same name but different configs and OAuth logins in different projects. I renamed the supabase server in one project, logged out from the server in both, and then OAuth worked in both and I can access both projects just fine. It's weird I didn't have this issue before upgrading versions, but everything is all good now.

@percusser commented on GitHub (Jan 24, 2026): I figured it out! I guess opencode doesn't like when there are MCP servers with the same name but different configs and OAuth logins in different projects. I renamed the supabase server in one project, logged out from the server in both, and then OAuth worked in both and I can access both projects just fine. It's weird I didn't have this issue before upgrading versions, but everything is all good now.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7451