Supabase MCP auth returns Unrecognized client_id on Windows and macOS #9225

Open
opened 2026-02-16 18:11:56 -05:00 by yindo · 1 comment
Owner

Originally created by @j-token on GitHub (Feb 12, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

When running opencode mcp auth for a Supabase MCP server, authentication fails with:

{"message":"Unrecognized client_id"}

Configuration

"supabase-dev": {
  "type": "remote",
  "url": "https://mcp.supabase.com/mcp?project_ref=(masked)&read_only=true",
  "enabled": true
}

Steps to reproduce

  1. Add the Supabase MCP configuration above.
  2. Run opencode mcp auth for supabase-dev.
  3. Follow the auth flow.
  4. Observe the error response.

Expected behavior

Supabase MCP auth should recognize the client and complete successfully.

Actual behavior

Auth fails with Unrecognized client_id.

Environment

  • Windows 10: reproducible
  • macOS: reproducible
  • MCP server: Supabase
Originally created by @j-token on GitHub (Feb 12, 2026). Originally assigned to: @rekram1-node on GitHub. ## Description When running `opencode mcp auth` for a Supabase MCP server, authentication fails with: ```json {"message":"Unrecognized client_id"} ``` ## Configuration ```json "supabase-dev": { "type": "remote", "url": "https://mcp.supabase.com/mcp?project_ref=(masked)&read_only=true", "enabled": true } ``` ## Steps to reproduce 1. Add the Supabase MCP configuration above. 2. Run `opencode mcp auth` for `supabase-dev`. 3. Follow the auth flow. 4. Observe the error response. ## Expected behavior Supabase MCP auth should recognize the client and complete successfully. ## Actual behavior Auth fails with `Unrecognized client_id`. ## Environment - Windows 10: reproducible - macOS: reproducible - MCP server: Supabase
Author
Owner

@github-actions[bot] commented on GitHub (Feb 12, 2026):

This issue might be related to existing Supabase MCP authentication issues:

  • #6842: Supabase MCP - Shows different errors (401 Unauthorized, Dynamic client registration failed)
  • #10602: Can't Auth MCP Server -- Authentication failed - General MCP auth failures

Consider reviewing these issues as they may provide additional context or workarounds.

@github-actions[bot] commented on GitHub (Feb 12, 2026): This issue might be related to existing Supabase MCP authentication issues: - #6842: Supabase MCP - Shows different errors (401 Unauthorized, Dynamic client registration failed) - #10602: Can't Auth MCP Server -- Authentication failed - General MCP auth failures Consider reviewing these issues as they may provide additional context or workarounds.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9225