Connect Supabase

Agents list projects, inspect tables, run SQL, apply migrations, deploy edge functions and read logs; you sign in to Supabase and pick an organisation.

Once Supabase is connected, an agent can list your projects, inspect tables and extensions, run SQL, apply schema changes as migrations, deploy edge functions, and read logs and the security and performance advisors.

Before you start

A Supabase account that is a member of the organisation whose projects you want to use.
Think about what the agents should reach. The connection covers one organisation and all of its projects, and SQL runs with real access. Many teams connect an organisation that holds staging projects, or keep production changes behind branches. Development branches need a paid plan.
You must be an owner or admin of the woble workspace.

Nothing to copy: Supabase uses a sign-in flow.

Connect it

Open Marketplace, go to the Integrations tab, find Supabase and press Connect.
Press Continue with Supabase. A new tab opens at supabase.com. Sign in if you are not already.
Supabase asks which organisation to grant access to. Pick it from the list and press Authorize.
The tab closes. The card shows Connected and the agent panel lists the new Supabase tools.

The agent lists projects when it does not know the project ref, and checks the schema with the table tools before writing SQL.

Or ask an agent

Type @ruby connect Supabase in any chat. The same card appears in the conversation. Only owners and admins can complete it.

Try it

"@atlas in the staging project, describe the orders table and show the ten most recent rows with status failed."
"@ruby create a development branch on the api project and add an index on invoices(customer_id) as a migration there."

If it does not connect

Wrong organisation: the agent lists projects you did not expect, or none. Press Remove in Marketplace, Connected, and connect again picking the right organisation.
Access revoked: the authorisation was removed in your Supabase account settings, or you left the organisation. Press Test connection; if it fails, Remove and reconnect.
Branch tools fail: development branches are a paid feature. The rest of the tools still work.

Disconnect

Open Marketplace, Connected, and press Remove on Supabase. The tokens are deleted and agents lose the Supabase tools immediately. You can also revoke the authorisation in your Supabase account settings.