Supabase MCP Connection Error

### What happened?

Error it gave me: ofid_aa5ac8f7f1d88526

Hello! This is my supabase read only mcp from the server. It works as a knowledge base sort of system for my claude chats. It was running fine on multiple platforms, and then when I went today, it was not pulling from there. Saying it was disconnected, Went to reconnect, and it did not, giving me that error code. Previously working fine with no issues and visibly reading from it to output a detailed response from what is integrated and embded into it.

### What did you expect to happen?

Read from the supabase server correctly.

### Steps to reproduce

1. Connected to MCP server
2. Call from it every time to each response, visibly read from supabase kb.
3. Output response

### Area

MCP Connector (adding/managing servers)

### MCP Server (if applicable)

Supabase Custom MCP

### Error messages or logs

```shell
Couldn’t register with Supabase KB’s sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: “ofid_aa5ac8f7f1d88526”
```

### Additional context

3. The suggested workaround (add an OAuth Client ID) is very likely a dead end for this specific connector, since there's no OAuth provider set up on the Supabase side at all — this connector was never built with a client ID/secret to enter.

Start in the MCP Connector (adding/managing servers) flow and reproduce the failure with the Supabase Custom MCP using reference “ofid_aa5ac8f7f1d88526”. Trace the sign-in or registration path and the OAuth Client ID workaround described in the report. Done means the connector reconnects and reads from the Supabase server without requiring an unsupported OAuth setup.

Escrito por el modelo de indexación a partir del texto del issue.