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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which branches on the checkout project have unmerged diffs?
Working in Supabase with Elaichi
-
List all Supabase organization
-
Get single Supabase organization by ID
-
List all Supabase organization members
How to connect Supabase to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Supabase MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Supabase MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Supabase through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Supabase is logged.
-
Engineering
Review a branch before it merges
Ask what has changed on a Supabase branch, read the differences in plain language, and merge or push it once the team is satisfied.
-
Platform
Roll a broken branch back
When a change goes wrong, reset or restore the Supabase branch to a known good state without hunting through the dashboard.
-
Security
See who can reach each organization
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.
-
Platform
Retire legacy API keys in bulk
Pull up the legacy API keys still in use across your Supabase projects and update them together instead of one at a time.
-
IT
Get a custom domain live
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.
-
Security
Check network bans after an incident
Retrieve the current network bans on a Supabase project when traffic looks suspicious and confirm what is blocked.
Try asking
- “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.”
What connecting Supabase gets you
6 screens from Elaichi, each doing one job for your Supabase account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about branches, get an answer.
Type a question in plain language and read it back from live Supabase records.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Connect any MCP client to Supabase over OAuth, no SDK and no shared API key.
Tool catalog
169 Supabase tools are ready to call.
Branches, projects, organization members and API keys are covered without custom code.
Toolboxes
Every team gets its own toolbox.
Curate one Supabase toolbox per team so each group sees only relevant tools.
Shared connections
Teammates use branches, never the credential.
See who connected each Supabase account and which teams and members it reaches.
Audit log
Every branch merge has a name on it.
When, who, what happened, type and resource for each call against Supabase.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Supabase digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch branches
Supabase
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Supabase
Queued
Automations
A schedule fires, a digest ships.
Fetch Supabase branches, group them, draft a digest, approve it, post it back.
Supabase health
Refreshed 4 minutes ago · every 15 minutes · from the branches collection
Branches
1,284 ↓ 12%
Projects
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Branches created
Last 14 days
By team
Share of activity
Platform 34%
App engineering 27%
Release 21%
Security 18%
Collections and dashboards
Supabase numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Supabase tools for your AI agents
169 tools are ready to call through Elaichi's MCP endpoint the moment you connect Supabase, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Supabase in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot