Application Development
Supabase MCP connector
The Supabase connector brings your Supabase organizations, members, branches, API keys and custom domains to Claude, ChatGPT, Cursor and any MCP client, so each person can review and manage them in plain language, inside their own access, with every action logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Supabase to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Supabase once
-
Open Connections, choose Add connection, and pick Supabase.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Supabase. Supabase's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Supabase
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Supabase to 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.
Connect Supabase to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Supabase to 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.
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.
Use cases
What teams do with Supabase through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Supabase gets you
6 screens from the product, each doing one job for your Supabase account.
The agent
Ask about branches, get an answer.
Type a question in plain language and read it back from live Supabase records.
- branches
- projects
- organization members
- api keys
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect any MCP client to Supabase over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
169 Supabase tools are ready to call.
Branches, projects, organization members and API keys are covered without custom code.
- List all Supabase organization
- Get single Supabase organization by ID
- List all Supabase organization members
- List all Supabase me
Toolboxes
Every team gets its own toolbox.
Curate one Supabase toolbox per team so each group sees only relevant tools.
- Platform
- Application engineering
- Release
- Security
Shared connections
Teammates use branches, never the credential.
See who connected each Supabase account and which teams and members it reaches.
- Platform
- App engineering
- Release
- Security
Audit log
Every branch merge has a name on it.
When, who, what happened, type and resource for each call against Supabase.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Fetch Supabase branches, group them, draft a digest, approve it, post it back.
Supabase digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Supabase
Queued
Collections and dashboards
Supabase numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed on schedule.
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%
FAQ
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, 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 blocking merges, resets, deletions or key changes. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
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 and every other client.
Put Supabase in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.