# Supabase AI integration on Definable

> Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications

## What this connects

Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications

Vendor: https://supabase.com

## Tools available

**116** tools available. First 12:

- `SUPABASE_ALPHA_CREATE_API_KEY` — Create project api key — Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.
- `SUPABASE_ALPHA_DELETE_API_KEY` — Delete an API key from the project — Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
- `SUPABASE_ALPHA_DELETE_THIRD_PARTY_AUTH_INTEGRATION` — Delete third party auth config — Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.
- `SUPABASE_ALPHA_GET_THIRD_PARTY_INTEGRATION` — Get a third-party integration — Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.
- `SUPABASE_ALPHA_LIST_THIRD_PARTY_AUTH_INTEGRATIONS` — List third-party auth integrations for project — Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
- `SUPABASE_ALPHA_UPDATE_API_KEY` — Update an API key for the project — Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.
- `SUPABASE_APPLY_A_MIGRATION` — Apply a database migration — Tool to apply database migrations to a Supabase project. Use when you need to execute SQL schema changes, create tables, alter columns, or run other DDL/DML operations as part of a tracked migration. This is a Beta feature in the Supabase Management API.
- `SUPABASE_BETA_ACTIVATE_CUSTOM_HOSTNAME` — Beta activate custom hostname for project — Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally.
- `SUPABASE_BETA_ACTIVATE_VANITY_SUBDOMAIN` — Activate vanity subdomain for project — Activates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co'). Important notes: - Vanity subdomains require a paid plan (Pro/Team/Enterprise) - Usage of vanity subdomains and custom domains is mutually exclusive - After activation, your project's auth services will no longer work on the original {project-ref}.supabase.co hostname - Schedule a downtime window to update client code and OAuth providers before activating
- `SUPABASE_BETA_AUTHORIZE_USER_THROUGH_OAUTH` — Authorize user through OAuth — Generates a Supabase OAuth 2.0 authorization URL for user redirection. IMPORTANT: This action requires a pre-registered OAuth client_id and a redirect_uri that matches one of the pre-registered URIs for that OAuth application. Without a valid registered OAuth application, this endpoint will return a 400 error. To use this action: 1. Register an OAuth application in the Supabase dashboard 2. Use the client_id from the registered application 3. Ensure redirect_uri matches one of the registered callback URLs
- `SUPABASE_BETA_CHECK_VANITY_SUBDOMAIN_AVAILABILITY` — Check vanity subdomain availability — Checks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain.
- `SUPABASE_BETA_CREATE_READ_REPLICA` — Setup read replica for project — Provisions a read-only replica for a Supabase project in a specified, Supabase-supported AWS region to enhance read performance and reduce latency.

## Auth

Auth schemes: `OAUTH2`, `API_KEY`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use Supabase

Inside a Definable workflow, Supabase is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Supabase** — the Researcher (GPT-5.5) pulls context from Supabase (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Supabase** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Supabase (create record, post message, draft email).
- **Designer / Engineer → Distributor → Supabase** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Supabase (attach file, open PR comment, post status).

The Verifier checks every Supabase call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/
- databases — https://definable.ai/apps/category/databases/

## Related

- HTML page: https://definable.ai/apps/supabase/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt