Integration · Automate and collaborate

Supabase and Meteor AI agents

Connect Supabase to an internal Met: list projects and tables, review migrations, advisors and Edge Functions with Supabase's official MCP.

Book a demo See every integration

How does Supabase connect to Meteor?

With the Supabase ready connector, your Met uses Supabase's official MCP server with the permissions of the account the admin authorizes. It lists your projects and their tables, reviews migrations, Edge Functions and security and performance advisors, and searches the Supabase docs. Running SQL, applying migrations, deploying Edge Functions, creating, pausing or restoring projects and branch operations start turned off until the admin turns them on. Met's connection is not in read-only mode, and Supabase recommends not giving it to your customers: it is for an internal team Met.

What it automates

What a Meteor Met does with Supabase

Answer the team with a fact from the database

When someone on the team asks on WhatsApp how an order is going or how many customers signed up today, the Met finds the project, checks the tables and, if the admin turned on the SQL query, which starts turned off, runs a read query to reply with the fact.

Review security and performance advisors

The Met brings the advisors Supabase computes for the project and sums up which are about security and which about performance, so the team decides what to handle.

See what changed in the database

The Met lists the applied migrations and the project's Edge Functions, and tells you which was the latest, without touching anything.

Try a change on a branch

If your plan includes branches and the admin turns on the action, which starts turned off, the Met creates a development branch to try a change before taking it to the main database. Creating the branch can incur charges.

24 tools

Everything your Met can ask Supabase for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_organizations`	Lists the Supabase organizations of the connected account.
`list_projects`	Lists the Supabase projects of the connected account.
`get_project`	Returns the details of a Supabase project.
`get_cost`	Reports the cost of creating a project or a branch, in the legacy cost confirmation workflow.
`confirm_cost`	Confirms that cost and returns the ID that create_project or create_branch ask for. Starts turned off.
`create_project`	Creates a new Supabase project. Supabase counts it among the actions that incur additional charges. Starts turned off.
`pause_project`	Pauses a Supabase project. Starts turned off.
`restore_project`	Restores a Supabase project. Starts turned off.
`list_branches`	Lists a project's development branches. Branches are experimental and need a paid plan.
`create_branch`	Creates a development branch of the database. It can incur charges and needs a paid plan. Starts turned off.
`delete_branch`	Deletes a development branch. Starts turned off.
`merge_branch`	Merges a development branch, one of Supabase's branch operations. Starts turned off.
`reset_branch`	Resets a development branch, one of Supabase's branch operations. Starts turned off.
`rebase_branch`	Rebases a development branch, one of Supabase's branch operations. Starts turned off.
`list_tables`	Lists all the tables in the database.
`list_migrations`	Lists the database migrations.
`apply_migration`	Applies a migration to the database. Starts turned off.
`execute_sql`	Runs SQL queries on the database. Starts turned off; outside read-only mode, which Met does not turn on, it can also write.
`get_advisors`	Returns the project's security and performance advisors.
`get_project_url`	Returns a project's API URL.
`search_docs`	Searches the Supabase documentation.
`list_edge_functions`	Lists all the project's Edge Functions.
`get_edge_function`	Returns a specific Edge Function.
`deploy_edge_function`	Deploys an Edge Function to the project. Starts turned off.

The limits

What the Supabase integration does NOT do

We would rather say it here than have you find out during rollout.

It does not work in read-only mode. Met connects to the URL without parameters, so if the admin turns on the SQL query or migrations, which start turned off, they can write with your permissions. Supabase recommends read-only and a scoped project for production.
It is not for serving your customers. Supabase recommends not giving it to customers or end users, because it runs with developer permissions: use it with an internal team Met.
It does not ask you for confirmation in the chat before writing, applying a migration or creating a project. Those actions, the branch ones and deploying Edge Functions start turned off; if the admin turns them on in Connections, the Met runs them.
It is not immune to instructions hidden in the data. Supabase wraps SQL results with warnings so commands inside the content are not followed, and says this is not foolproof.
It does not include Storage. That tool group comes turned off by default in Supabase and Met's connection does not turn it on.
It does not pay your Supabase plan. Creating projects or branches can incur charges on your account; Meteor does not resell the service.

Before you start

What you need to connect Supabase

1

A Supabase account with the project

The account your team manages the project with. When authorizing you choose the organization that contains the project, and the Met works with that account's permissions.
2

Connect it in Met

In Met, open Connections → Supabase → Connect. A Supabase window opens so you sign in and authorize Met. Then the admin chooses which actions stay on.
3

A paid plan to use branches

The branch tools are experimental and Supabase keeps them for paid plans. Everything else works without them.

Frequently asked questions

Questions about Supabase and Meteor

No. Supabase turns read-only on with a URL parameter, and Met uses the URL without parameters. The SQL query and the other write actions start turned off. If the admin turns on the SQL query, tell the Met in its instructions to only read: the query itself does not prevent it.

Supabase recommends against it: the server runs with your developer permissions. Use it in an internal Met that only serves the team.

Only if the admin turns on the action, which starts turned off. Supabase counts creating projects and branches among the actions that incur additional charges; get_cost and confirm_cost exist to report that cost.

You do, with your Supabase account and plan. Meteor does not resell Supabase: the connector uses your company's account.

Step by step