Integrations · Development

Connect Supabase to Well

Connect Supabase to make it reachable from conversation and your agents in Well. Supabase exposes no structured records to sync today, so this is a reach connection, not a data feed.

Connect SupabaseSee what Well does

What Well pulls from Supabase

Supabase feeds Supabase into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Supabase’s access.

From Supabase		In Well	Relation
Supabase		Workspace context	Reachable from

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Supabase → Well

What Well does with your Supabase connection

Connect

Connect Supabase over OAuth (MCP DCR): Well registers a client through Supabase's OAuth Dynamic Client Registration and you approve on Supabase's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Connecting Supabase makes it reachable from your workspace; Supabase exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Supabase adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Supabase is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Supabase unlocks

Ask in plain language. Well answers from your connected Supabase connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Supabase connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Supabase connection…

Connect Supabase in three steps

01
Authorise Supabase via MCP
From Well's Connections panel, search for Supabase and click Connect. Well discovers Supabase's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Supabase's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.supabase.com/mcp
02
Make it reachable
The connection puts Supabase within reach of your workspace and its agents. Supabase exposes no structured record for Well to map into an invoice, transaction, or account today, so there is no records table to set up and Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach Supabase in the same place it reaches the rest of your stack. If Supabase later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Supabase stays secure with Well

Well connects to Supabase's MCP server (mcp.supabase.com/mcp) via the Model Context Protocol. The MCP server handles credential issuance through OAuth Dynamic Client Registration, so Well never holds a long-lived Supabase secret. Because Supabase maps no structured entity today, the token simply makes Supabase reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Supabase.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.supabase.com/mcp

Read Supabase records
Resources the Supabase MCP server exposes, scoped by your OAuth approval.
granted
Reach Supabase from your workspace
The grant makes Supabase reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Supabase.
granted
Modify or delete Supabase records
Not granted; Supabase is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Supabase passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Supabase’s admin panel.

Frequently asked questions about Supabase and Well

How do I connect Supabase to Well, and how long does it take?

Choose Supabase in Well's Connections panel and authorise it over its MCP server. Well discovers the OAuth metadata from the MCP endpoint and registers a client via Dynamic Client Registration, so there are no keys to paste. The handshake completes in about a minute and puts Supabase within reach of your workspace and its agents.

What does Well sync from Supabase today?

No structured record, and the page is candid about that. Supabase exposes no supported target model for Well to turn into an invoice, transaction, or account, so there is no records table to configure and nothing is pulled into your workspace. The connection is about reach, not a data feed.

If nothing is synced, what does connecting Supabase give me?

It lets an agent working in your workspace reach Supabase in the same place it reaches the rest of your stack, instead of treating it as a separate destination. This is a reach-and-availability connection: honest about not pulling structured records that Supabase does not expose.

Will Supabase ever bring records into the workspace?

Only if and when Supabase exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller; if that changes, the data-flow section would reflect the real entities.

What happens if I disconnect Supabase?

Disconnecting Supabase in Well revokes the OAuth token and ends the MCP reach immediately. Because nothing structured was being synced, there are no workspace records to retain or purge; it simply removes Supabase from the set of tools your agents can reach through Well.