Answers questions with read-only Postgres queries, inspects table schemas, applies migrations, deploys edge functions, and reports project health.
116actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro 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.
Ayro 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.
Ayro 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.
Each card is one request a support team gets, and the Supabase actions Ayro runs to close it.
Ayro 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.
When a change is agreed, Ayro applies it as a tracked migration rather than an ad hoc statement, and can regenerate the TypeScript types that follow from it.
Ayro 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.
Ayro pulls service health, project logs, and the list of database backups, so the first pass at an incident happens before anyone opens the dashboard.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Supabase actions it has and picks the ones a request needs.
Authorize the Supabase account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Supabase actions that close it and chains as many as the request needs.
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 freeSupabase · Ayro
What can you do in Supabase without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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 Ayro is allowed to reach is decided by the Supabase access token you connect and the scopes on it.
All 116 actions your agent can call on Supabase, straight from the live MCP connection.
Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.
Permanently deletes a specific API key (identified by id) from a Supabase project (identified by ref), revoking its access.
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.
Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by tpa_id, within an existing Supabase project specified by ref.
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.
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 database migrations to a Supabase project.
Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally.
Activates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co').
Generates a Supabase OAuth 2.0 authorization URL for user redirection.
Checks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain.
Provisions a read-only replica for a Supabase project in a specified, Supabase-supported AWS region to enhance read performance and reduce latency.
Enables database webhooks for the Supabase project ref, triggering real-time notifications for INSERT, UPDATE, or DELETE events.
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.
Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation.
Retrieves the network restriction settings (IP allowlists) for a Supabase project.
Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its ref.
Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database.
Fetches the current vanity subdomain configuration, including its status and custom domain name, for a Supabase project identified by its reference ID.
Removes specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored.
Remove a read replica from a Supabase project (Pro plan or higher required).
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.
Updates and applies network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project, which may terminate existing connections not matching the new rules.
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.
Counts the number of action runs for a Supabase project using a HEAD request.
Creates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.
Bulk create secrets for a Supabase project.
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.
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.
Creates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks.
Same connection, same setup. Pick the next one your team already uses.
Reads a base, answers from its records, creates and updates rows from a live conversation, and leaves comments for the next person.
Runs SQL and returns results, explores the databases and tables a role can reach, and checks platform status when a query drags.
Confirms a board is online, reads analog sensor values, switches digital pins high or low, and exchanges serial data over UART.
Renders HTML into PDF or PNG, merges PDFs from public URLs, and drives a sandboxed headless Puppeteer script.
Grafbase is a platform for building and scaling GraphQL APIs with edge caching and unified data access.
Searches the registry, reads package metadata and dist-tags, pulls download counts by version or date range, and bulk-checks security advisories.

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