Connect Supabase to ChatGPT. For your whole team.
The official Supabase MCP signs in one developer. Unless somebody remembered read_only and project_ref, it can apply migrations on every project that developer can reach. Loopthink holds one scoped read-only token for one project, gives every ChatGPT user in your team their own login, and lets Data, Support and Management query exactly the tables their role allows.
Free for your own server · Team from €99 · EU-hosted
Supabase in a chat client, today.
Today a team that wants Supabase in an AI client either gives everyone a dashboard seat, or one developer pastes their access token into a shared config. A classic token carries every permission on every project of that account, and the MCP server runs SQL with the developer's rights. Supabase's own docs warn about prompt injection pulling data out of a production table, and no log says who ran it.
One matrix for Supabase. Roles across, tools down.
| Tool | Data | Support | Management |
|---|---|---|---|
| Tables & schema | Data may use Tables & schema | Support may not use Tables & schema | Management may use Tables & schema |
| Query data | Data may use Query data | Support may use Query data | Management may use Query data |
| Logs | Data may use Logs | Support may not use Logs | Management may not use Logs |
| Advisors & lints | Data may use Advisors & lints | Support may not use Advisors & lints | Management may not use Advisors & lints |
| Edge functions | Data may use Edge functions | Support may not use Edge functions | Management may not use Edge functions |
| Write actions off by default | Data may not use Write actions | Support may not use Write actions | Management may not use Write actions |
Masked for every role: email and phone columns in query results, connection strings and secrets, IP addresses in logs.
You set this once. Every ChatGPT user in your team gets exactly this.
Once on the Supabase side, once in ChatGPT.
On the Supabase side
Scoped personal access token, read-only, one project
- 1
Supabase Dashboard → Account → Access Tokens (supabase.com/dashboard/account/tokens) → Generate new token.
- 2
Choose a scoped token: one organisation, one project, read permission on Database, Logs and Edge Functions. Supabase recommends scoped tokens for every AI agent.
- 3
Paste the token and the project reference into Loopthink. It runs read-only and never reaches the AI client.
In ChatGPT
Custom connector, OAuth
- 1
An admin turns on Developer mode: Settings → Apps → Advanced settings. On Enterprise and Edu, admins first grant it under Permissions & Roles → Connected Data.
- 2
Workspace settings → Apps → Create: paste your Loopthink connector URL, choose OAuth, click Scan Tools, then Create. Publish the draft under Workspace settings → Apps → Drafts.
- 3
Each team member picks Loopthink from the tools menu in a chat, or @mentions it, and signs in once with their own account.
Full MCP apps are available on ChatGPT Business, Enterprise and Edu; Pro can connect read-only MCP servers in developer mode. Published apps show up in every member's Apps settings with the label custom.
Steps checked against the vendor documentation on 17 September 2026: Supabase MCP server · Personal access tokens · Management API introduction · Developer mode and MCP apps in ChatGPT · Connectors in ChatGPT
Loopthink sits in between: it holds the key, shows ChatGPT a normal login, and applies your roles on every call.
Four checks between ChatGPT and Supabase.
- 01
Identify
OIDC/SSO against your own IdP, including Microsoft Entra. The call runs as the person who made it, never as a shared service account.
- 02
Authorize
Per-role, per-tool, read or write. Anything not explicitly granted never shows up in the tool list in the first place.
- 03
Mask
Field-level masking and pseudonymization applied on your side, before the result travels. The model never sees the raw field. Composio, AnythingMCP and both provider tunnels have no field-level masking at all.
- 04
Log
Who asked, which tool, which records, which fields were masked. One audit trail across every AI client, exportable for review.
What people actually ask ChatGPT about Supabase.
- Data
“How many rows landed in orders yesterday, broken down by country?”
- Support
“Find the orders for customer 4711 and tell me whether the last one shipped.”
- Management
“Sign-ups this week versus last week?”
Each question runs as the person who asked it, with that person's role. A Support colleague asking the Data question gets the tools their own role allows, not an error, not more.
Four ways to put Supabase into ChatGPT.
| Native Supabase connector | Build it yourself | Enterprise gateways1 | Loopthink | |
|---|---|---|---|---|
| Per-user identity | One personal login, all its rights | Only if you build it | Yes | Yes, every call runs as the person who asked |
| Tool-level roles | No | Your code | Yes | Yes, write off by default |
| Field masking | No | Your code | Not documented | Yes, before the model sees the data |
| Published price | Included in your Supabase plan | Your engineers' time | Contact sales | Free, Team from €99 |
| EU company | No | Whatever you are | Mostly US | Yes, Germany |
Native Supabase connector: Official Supabase MCP with OAuth. One developer's permissions, every project of the account, read-only and project scoping optional.
1 MintMCP, MCP Manager, Pomerium
Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative
Also for
Connect another system to ChatGPT
Before you connect.
- Does every team member need their own Supabase account?
- No. Loopthink holds one key or token for Supabase. Your people sign in to Loopthink with their own identity, and every call to Supabase is logged under their name. Seats in Supabase stay where they are today.
- Who has to add the connector in ChatGPT?
- One person with the right to add connectors in your ChatGPT workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
- Where does the Supabase key live?
- In Loopthink, encrypted, in the EU. It never reaches ChatGPT and never reaches the people using the connector. Rotate it in Supabase whenever you like and paste the new one once.
- Can somebody write to Supabase from the chat?
- Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
- What does the model see?
- The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to ChatGPT. The model gets the numbers, not the people.
- Is there an audit trail?
- Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.
- What does it cost?
- Free for one person and your own MCP server, forever. Team starts at €99 per month and covers the built connector, per-person identity, roles, masking and audit for the whole team. Prices are on the pricing page, no call needed.
- We already run our own MCP server for Supabase. Does it still work?
- Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.
Supabase in ChatGPT, with rules.
One key in Loopthink, one login per person, one matrix that decides who may do what.
Free for your own server · Team from €99 · EU-hosted