# Supabase MCP connector

The Supabase connector brings your Supabase organizations, members, branches, API keys and custom domains to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person can review and manage them in plain language, inside their own access, with every action logged.

Source: https://elaichi.ai/connectors/supabase/

## Facts

| | |
| --- | --- |
| Application | Supabase |
| Category | Application Development |
| AI tools | 169 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Supabase is connected

- Which branches on the checkout project have unmerged diffs?
- Show every member of our Supabase organization by role.
- List legacy API keys still active across production projects.

## Connect Supabase in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Supabase.
2. Optionally set Share with, then press Connect.
3. Approve it in Supabase. Supabase's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Supabase tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Supabase MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Supabase MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Supabase MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Supabase MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Supabase MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Supabase to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a Supabase tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Run your connected tools, which can also delete in connected apps and cannot be undone.

## What teams do with Supabase through Elaichi

### Review a branch before it merges

Engineering. Ask what has changed on a Supabase branch, read the differences in plain language, and merge or push it once the team is satisfied.

### Roll a broken branch back

Platform. When a change goes wrong, reset or restore the Supabase branch to a known good state without hunting through the dashboard.

### See who can reach each organization

Security. List the members of every Supabase organization and the apps that have been authorized against it, then revoke anything that should no longer be there.

### Retire legacy API keys in bulk

Platform. Pull up the legacy API keys still in use across your Supabase projects and update them together instead of one at a time.

### Get a custom domain live

IT. Start the custom hostname setup for a Supabase project, check verification when the DNS record is in place, and activate it, all from one conversation.

### Check network bans after an incident

Security. Retrieve the current network bans on a Supabase project when traffic looks suspicious and confirm what is blocked.

## Elaichi vs Zapier MCP vs Composio for Supabase

All three can connect Supabase to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Supabase tools | Allow or restrict single Supabase tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Supabase call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Supabase to Claude?

Connect Supabase in Elaichi first: click connect, sign in to your Supabase account, and approve the access it asks for. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Supabase is available in Claude.

### Does Supabase work with ChatGPT and Cursor as well as Claude?

Yes. Once Supabase is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Supabase once and every client picks it up.

### What can an AI agent actually do with my Supabase account?

Through Elaichi, an agent can list your Supabase organizations and their members, show what has changed on a branch and merge, push, reset or restore it, review and update legacy API keys, set up and activate a custom domain, check network bans, and see or revoke the apps authorized against your account. Because Supabase exposes a large number of actions, short concrete asks such as "show the diff on the staging branch" work better than long paragraphs.

### Does connecting Supabase give the AI access to all my organizations and projects?

No. The agent works inside the access of the person who signed in to Supabase, so it sees only the organizations, projects and branches that person can already reach in Supabase itself. Elaichi can narrow that further with restrictions on individual actions, and it can never widen it beyond what Supabase grants that person.

### Can my team share one Supabase connection?

Yes. One person connects Supabase in Elaichi and shares the connection with a team, and nobody else ever handles a credential or generates a key. Each teammate still signs in to Elaichi as themselves, so every action against Supabase is recorded under the name of the person who asked for it.

### Can I stop an agent from deleting or changing things in Supabase?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Supabase branches and members while restricting merges, resets, deletions or key changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.

### What happens to a Supabase connection when someone leaves?

Offboarding a person in Elaichi ends their access to Supabase through every connected client at once. A Supabase connection shared with a team keeps working for everyone else on that team. If you want to remove Supabase entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Supabase MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Supabase is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Supabase?

Yes. Both let Claude, ChatGPT or Cursor use Supabase. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Supabase call.

### How is Elaichi different from Composio for Supabase?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Supabase: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 169 Supabase tools

Every tool below is callable through https://api.elaichi.ai/mcp once Supabase is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Supabase organization** (List). List all Supabase organizations that you currently belong to. Returns: id, slug, name.
- **Get single Supabase organization by ID** (Get). Get information about a specific Supabase organization by id (organization slug). Returns: id, name, plan, opt_in_tags, allowed_release_channels, slug. Required: id.
- **List all Supabase organization members** (List). List members of a Supabase organization. Returns: user_id, user_name, email, role_name, mfa_enabled, avatar_url. Required: organization_id.
- **List all Supabase me** (List). Get the authenticated Supabase user's profile from the Management API. Returns: gotrue_id, primary_email, username.
- **Supabase action status bulk update** (Update). Update the status of an action run. Returns: message. Required: ref, run_id.
- **Supabase API keys legacies bulk update** (Update). Enable or disable JWT-based legacy (anon, service_role) API keys for a Supabase project. Returns the keys array containing each legacy API key's id, algorithm, status, public_jwk, created_at, and updated_at. Required: ref, enabled. Deprecated — may return 404 in the future.
- **List all Supabase API keys legacies** (List). Check whether JWT-based legacy (anon, service_role) API keys are enabled for a Supabase project. Returns the keys array containing each legacy API key's id, algorithm, status, public_jwk, created_at, and updated_at. Required: ref. Deprecated — may return 404 in the future.
- **List all Supabase authorize project claims** (List). Initiate the Supabase OAuth authorization flow to claim ownership of a specified project. Returns an empty 204 response on success. Required: project_ref, client_id, response_type, redirect_uri.
- **List all Supabase branche diffs** (List). Get the schema diff for a Supabase database branch. Returns the diff output as a plain text string containing SQL statements representing schema differences between the branch and its parent. Required: branch_id_or_ref. This is a Beta endpoint.
- **Create a Supabase branche merge** (Create). Merge a Supabase database branch identified by branch_id_or_ref into its parent branch. Returns: workflow_run_id, message. Required: branch_id_or_ref.
- **Create a Supabase branche push** (Create). Pushes a database branch. Returns: workflow_run_id, message. Required: branch_id_or_ref.
- **Supabase branches bulk delete** (Delete). Delete a Supabase database branch by branch_id_or_ref. By default, deletes immediately; set force to false to schedule deletion with a 1-hour grace period when soft deletion is enabled. Returns: message. Required: branch_id_or_ref.
- **Supabase branches bulk update** (Update). Update the configuration of a Supabase database branch by branch_id_or_ref. Returns: id, name, project_ref, parent_project_ref, is_default, git_branch, pr_number, latest_check_run_id, persistent, status, created_at, updated_at, review_requested_at, with_data, notify_url, deletion_scheduled_at, preview_project_status. Required: branch_id_or_ref, requestedConfig.
- **List all Supabase branches** (List). Get the configuration of a Supabase database branch by branch_id_or_ref. Returns: ref, postgres_version, postgres_engine, release_channel, status, db_host, db_port, db_user, db_pass, jwt_secret, id, name, project_ref, parent_project_ref, is_default, git_branch, pr_number, latest_check_run_id, persistent, created_at, updated_at, review_requested_at, with_data, notify_url, deletion_scheduled_at,…
- **Supabase branches reset** (Action). Reset a Supabase database branch by branch_id_or_ref, optionally targeting a specific branch name or rollback point. Returns: workflow_run_id, message. Required: branch_id_or_ref.
- **Supabase branches restore** (Restore). Restore a scheduled deletion of a Supabase database branch by branch_id_or_ref, cancelling the scheduled deletion and restoring the branch to active state. Returns: message. Required: branch_id_or_ref.
- **Create a Supabase custom hostname activate** (Create). Activate a custom hostname for a Supabase project (beta endpoint). Returns: status, custom_hostname, data, custom_domain. Required: ref.
- **Create a Supabase custom hostname initialize** (Create). Initialize a custom hostname configuration for a Supabase project. Returns: status, custom_hostname, data. Required: ref, custom_hostname. Beta endpoint.
- **Create a Supabase custom hostname reverify** (Create). Reverify the DNS configuration for a Supabase project's custom hostname, returning the updated configuration status and verification data. Returns: status, custom_hostname, data, custom_domain. Required: ref.
- **Create a Supabase network bans retrieve** (Create). Retrieve a Supabase project's network bans by project ref. Returns: banned_ipv4_addresses. Required: ref. This is a beta endpoint.
- **List all Supabase oauth authorizes** (List). Initiate a Supabase OAuth authorization flow for a user. Returns an empty 204 response on success — the authorization code or token is delivered to the redirect URI as part of the OAuth redirect. Required: client_id, response_type, redirect_uri. Beta endpoint.
- **Create a Supabase oauth revoke** (Create). Revoke a Supabase OAuth app authorization and its corresponding tokens (beta). Returns an empty 204 response on success. Required: email, token.
- **Create a Supabase oauth token** (Create). Exchange an authorization code, refresh token, or JWT bearer assertion for a Supabase user's access and refresh token. Returns: access_token, refresh_token, expires_in, token_type. The jwt-bearer grant type (IDJAG) is in beta and available on Team and Enterprise plans only.
- **Create a Supabase organization** (Create). Create an organization. Returns: id, slug, name. Required: name.
- **List all Supabase profiles** (List). Get the current user's Supabase Management API profile. Returns: gotrue_id, primary_email, username.
- **Get single Supabase project action by ID** (Get). Get the status of a Supabase action run by id. Returns: id, branch_id, run_steps, git_config, workdir, check_run_id, created_at, updated_at, run_id, status. Required: ref, id.
- **List all Supabase project actions** (List). List all Supabase action runs for a project. Returns: id, branch_id, run_steps, git_config, workdir, check_run_id, created_at, updated_at. Required: ref.
- **Supabase project actions list logs** (List). Get the logs of a Supabase action run as plain text. Returns the log output as a plain-text string. Required: ref, run_id.
- **Create a Supabase project API key** (Create). Creates a new API key for the project. Returns: api_key, id, type, prefix, name, description, hash, secret_jwt_template. Required: ref, type, name.
- **Delete a Supabase project API key by ID** (Delete). Delete a Supabase project API key. Returns the deleted API key object including id, api_key, type, prefix, name, description, hash, secret_jwt_template, inserted_at, and updated_at. Required: ref, id. The id must be a UUID-formatted string and ref must be exactly 20 lowercase letters.
- **Get single Supabase project API key by ID** (Get). Get a specific Supabase project API key by its id. Returns: api_key, id, type, prefix, name, description, hash, secret_jwt_template, inserted_at, updated_at. Pass reveal=true to include the full api_key value. Required: ref, id.
- **List all Supabase project API keys** (List). List all API keys for a Supabase project. Returns: api_key, id, type, prefix, name, description, hash, secret_jwt_template, inserted_at, updated_at. Required: ref. Set reveal to a truthy value to include full key values in the response.
- **Update a Supabase project API key by ID** (Update). Update a Supabase project API key's name, description, or secret JWT template by id. Returns: api_key, id, type, prefix, name, description, hash, secret_jwt_template, inserted_at, updated_at. Required: ref, id.
- **Supabase project branches bulk delete** (Delete). Disable preview branching for a Supabase project. Returns an empty 200 response on success. Required: ref.
- **Create a Supabase project branch** (Create). Create a database branch from a Supabase project. Returns the created branch object including id, name, project_ref, parent_project_ref, is_default, git_branch, persistent, status, created_at, updated_at, review_requested_at, with_data, notify_url, deletion_scheduled_at, and preview_project_status. Required: ref, branch_name.
- **List all Supabase project branches** (List). List all database branches of a Supabase project. Returns each branch with id, name, project_ref, parent_project_ref, is_default, git_branch, persistent, status, created_at, updated_at, review_requested_at, with_data, notify_url, deletion_scheduled_at, and preview_project_status. Required: ref.
- **List all Supabase project branches projects** (List). Get a Supabase database branch by project ref and branch name. Returns: id, name, project_ref, parent_project_ref, is_default, git_branch, pr_number, latest_check_run_id, persistent, status, created_at, updated_at, review_requested_at, with_data, notify_url, deletion_scheduled_at, preview_project_status. Required: ref, name.
- **Supabase project custom hostnames bulk delete** (Delete). Delete a Supabase project's custom hostname configuration. Returns an empty 200 response on success. Required: ref.
- **List all Supabase project custom hostnames** (List). Get a Supabase project's custom hostname configuration. Returns: status, custom_hostname, data, custom_domain. Required: ref.
- **Supabase project jit acceses bulk update** (Update). Update a Supabase project's temporary (JIT) access configuration by setting the desired state. Returns: state, appliedSuccessfully, unavailableReason. Required: ref, state.
- **List all Supabase project jit acceses** (List). Get a Supabase project's temporary (JIT) access configuration. Returns: state, appliedSuccessfully, unavailableReason. Required: ref.
- **Supabase project network bans bulk delete** (Delete). Remove network bans from a Supabase project by specifying the banned IPv4 addresses to unban. Returns an empty 200 response on success. Required: ref, banned_ipv4_addresses.
- **Supabase projects bulk delete** (Delete). Deletes the given project. Returns: id, ref, name. Required: ref.
- **Supabase projects bulk update** (Update). Update a Supabase project by its ref. Returns the updated project object including ref, name, cloud_provider, region, is_branch, status, and inserted_at. Required: ref, name. The ref must be exactly 20 lowercase letters.
- **Create a Supabase project** (Create). Create a new Supabase project in a specified organization. Returns: id, ref, organization_id, organization_slug, name, region, created_at, status. Required: organization_slug, name, db_pass. The organization_id, plan, region, and kps_enabled fields are deprecated.
- **Supabase projects get restore** (Get). List available restore versions for a Supabase project. Returns the available restore versions for the project. Required: ref (the project reference string, exactly 20 lowercase letters).
- **List all Supabase projects** (List). List all Supabase projects you've previously created. Returns each project's id, ref, name, region, status, organization_id, and database configuration details.
- **Supabase projects pause** (Pause). Pause a Supabase project by its project ref. Returns an empty response on success. Required: ref.
- **Supabase projects restore** (Restore). Restore a paused Supabase project by its project ref. Returns an empty response on success. Required: ref.
- **List all Supabase projects available regions** (List). List available Supabase regions that can be used when creating a new project, optionally filtered by continent and desired instance size. Returns the RegionsInfo object containing available regions for project creation. Required: organization_slug. This endpoint is in beta.
- ...and 119 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
