Connect Supabase to Well

From Well, open Connections, find Supabase, and click Connect. Well discovers the OAuth metadata at mcp.supabase.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Supabase's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in table row, project, and auth event from Supabase and reshapes each entity into your workspace: table row becomes indexed record; project becomes workspace context. Every record arrives with the source identifier preserved, so Supabase stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well links Supabase activity (issues, commits, deploys, runs) to the customer accounts in your CRM that originated each request. A bug report from a top-revenue customer shows that revenue context inline; a deploy mentions the customer-facing features that just shipped.

Each Supabase table row is scored against the candidate indexed records in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely indexed record prefilled and the Supabase source attached.

Well combines live Supabase events with periodic reconciliation reads of table row, project, and auth event. New rows appear within seconds when Supabase pushes them; periodic reads catch anything a push missed. The first connect backfills history from Supabase in the background.

Open Connections > Supabase in Well and click Disconnect. Well calls Supabase's token revocation endpoint and stops calling Supabase immediately on its side; provider-side propagation to Supabase's admin panel varies by provider. The table row, project, and auth event Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Supabase records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.