Connect your AI Agents to Supabase in minutes

What is a Supabase MCP?

It's an MCP server that lets your agents interact directly with Supabase's backend platform via tools. Your agents can invoke these tools to run SQL queries, manage database migrations, deploy edge functions, configure project settings, and more.

Supabase offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Supabase MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated schema migrations on merge: When a feature branch is merged in GitHub, an agent generates the corresponding Supabase migration, applies it to the staging database branch, and posts a schema diff to the pull request for review before it goes to production

• Database-driven product reporting: On a weekly schedule, an agent runs SQL queries against a Supabase database to aggregate retention, usage, or revenue metrics, formats the results into a readable summary, and posts them to the product team's Slack channel

• Project provisioning for new clients: When a new client engagement is created in a project management tool, an agent creates a Supabase project, applies the baseline schema, and stores the required API credentials as project secrets, ready for the dev team to use

• Edge function deployment on config change: When a configuration file is updated in a GitHub repository, an agent redeploys the affected Supabase edge function with the new code and confirms the deployment succeeded before closing the PR

What are popular tools for Supabase's MCP server?

Here are some of the most commonly used tools:

• execute_query: runs a SQL statement against a Supabase Postgres database and returns the results. Use this when an agent needs to read, insert, update, or delete data as part of any data-driven workflow

• create_migration: generates and applies a new database migration to a Supabase project or branch. Good for workflows where schema changes need to be versioned and applied in response to a code or deployment event

• list_projects: returns all Supabase projects in the account along with their status and configuration metadata. Helpful when an agent needs to identify the correct project before running queries or applying changes

• get_project_health: checks the health status of a specific project, including database and API availability. Call this when an agent needs to confirm a project is operational before executing operations or after a deployment completes

• create_edge_function: deploys a new edge function to a Supabase project with a specified name and code payload. Use this when an agent is provisioning serverless logic as part of a project setup or an automated release workflow

• create_secrets: stores environment secrets against a Supabase project, making them accessible to edge functions and server-side code. Use this when an agent is bootstrapping a new project and needs to configure third-party credentials without exposing them in source code

What makes Merge Agent Handler's Supabase MCP server better than alternative Supabase MCP servers?

Supabase has its own official MCP server, but there are good reasons to run Supabase through Merge Agent Handler in production environments:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Supabase, this means you can prevent database contents, API keys, auth configuration, and project secrets from being exposed even when the agent has broad access to the platform

• Managed authentication and credentials: Merge stores and manages your Supabase credentials on your behalf. You never inject service role keys or OAuth tokens directly into agent configuration, and you don't need to handle re-authentication as credentials change

• Real-time observability and audit trail: Every tool call against Supabase is logged: which query ran, which project was targeted, what the response contained. That record is searchable and available to your engineering and security teams without any custom instrumentation

• Tool Packs and controlled access: Tool Packs let you bundle specific Supabase tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Supabase MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack, then find and enable the Supabase connector. Choose the tools that fit your workflow: execute_query and list_projects cover most read and reporting use cases, while create_migration, create_edge_function, and create_secrets are needed for agents that provision or modify infrastructure.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Supabase by completing the OAuth flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Supabase tools are now accessible through that endpoint.