Supabase

Supabase MCP integration

Answers questions with read-only Postgres queries, inspects table schemas, applies migrations, deploys edge functions, and reports project health.

116actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Execute project database query

    Lyro runs a SQL query against a Supabase project's database to pull the exact record needed. Agents get the answer straight from the data instead of waiting on an engineer to look it up.

  • Create a function

    Lyro creates a new serverless Edge Function in a Supabase project from the code it's given. A new piece of backend logic goes live without a developer setting up the deployment by hand.

  • Enable project database webhooks

    Lyro turns on database webhooks for a Supabase project so changes trigger real-time notifications. The team hears about new inserts or updates immediately instead of checking the database manually.

See all 116 actions

How businesses use Supabase + Lyro

Each card is one request a support team gets, and the Supabase actions Lyro runs to close it.

  • Answer a question from live Postgres data

    Lyro lists the tables, reads the schema so it knows what the columns mean, and runs a read-only query, so an answer comes from the database instead of a stale export.

    List Database TablesGet Table SchemasExecute Read-Only Query
  • Ship a schema change through a real migration

    When a change is agreed, Lyro applies it as a tracked migration rather than an ad hoc statement, and can regenerate the TypeScript types that follow from it.

    Apply a Database MigrationList Migration HistoryGenerate TypeScript Types
  • Deploy and invoke edge functions

    Lyro deploys a function to the project and invokes it to confirm the behaviour, so a small backend change does not need a separate deploy session.

    Create a FunctionDeploy FunctionInvoke Edge Function
  • Check project health when something looks wrong

    Lyro pulls service health, project logs, and the list of database backups, so the first pass at an incident happens before anyone opens the dashboard.

    Get Service Health StatusGet Project LogsList Project Database Backups

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Supabase actions it has and picks the ones a request needs.

  1. 01

    Connect Supabase

    Authorize the Supabase account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Supabase actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Supabase · Lyro

Everything else about Supabase

Setup, permissions, and the limits of what Lyro can do inside Supabase.

  • Both actions exist and they are deliberately separate: Execute Read-Only Query cannot mutate data, while Execute Project Database Query and Apply a Database Migration can. Which one Lyro is allowed to reach is decided by the Supabase access token you connect and the scopes on it.

Every action available in Supabase

All 116 actions your agent can call on Supabase, straight from the live MCP connection.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • Apply a database migration

    Apply database migrations to a Supabase project.

  • Beta activate custom hostname for project

    Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally.

  • Activate vanity subdomain for project

    Activates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co').

  • Authorize user through oauth

    Generates a Supabase OAuth 2.0 authorization URL for user redirection.

  • 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.

  • 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.

  • Enable project database webhooks

    Enables database webhooks for the Supabase project ref, triggering real-time notifications for INSERT, UPDATE, or DELETE events.

  • Beta get project's custom hostname config

    Retrieves a Supabase project's custom hostname configuration, including its status, SSL certificate, and ownership verification, noting that availability may depend on the project's plan.

  • Retrieve network bans for project

    Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation.

  • Get project network restrictions

    Retrieves the network restriction settings (IP allowlists) for a Supabase project.

  • Get project pgsodium config

    Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its ref.

  • Get project ssl enforcement configuration

    Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database.

  • Get current vanity subdomain config

    Fetches the current vanity subdomain configuration, including its status and custom domain name, for a Supabase project identified by its reference ID.

  • Remove project network bans

    Removes specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored.

  • Remove read replica

    Remove a read replica from a Supabase project (Pro plan or higher required).

  • Execute project database query

    Executes a given SQL query against the project's database; use for advanced data operations or when standard API endpoints are insufficient, ensuring queries are valid PostgreSQL and sanitized.

  • Beta update project network restrictions

    Updates and applies network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project, which may terminate existing connections not matching the new rules.

  • Upgrade the project's postgresql version

    Initiates an asynchronous upgrade of a Supabase project's PostgreSQL database to a specified target_version from a selected release_channel, returning a tracking_id to monitor status; the target_version must be available in the chosen channel.

  • Count action runs

    Counts the number of action runs for a Supabase project using a HEAD request.

  • Create new project

    Creates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.

  • Bulk create secrets

    Bulk create secrets for a Supabase project.

  • Create a database branch

    Creates a new, isolated database branch from an existing Supabase project (identified by ref), useful for setting up separate environments like development or testing, which can optionally be linked to a Git branch.

  • Create a function

    Creates a new serverless Edge Function for a Supabase project (identified by ref), requiring valid JavaScript/TypeScript in body and a project-unique slug identifier.

  • Create cli login role

    Creates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks.

Ready to connect Supabase?

Authorize the account and your agent has all 116 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot