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 Claude?

One person with the right to add connectors in your Claude 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 Claude 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 Claude. 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.

Free for one person and two MCP servers, forever, no card. Starter is €39 per month and adds roles, an identity of their own for every colleague, field masking and a 30-day audit. Team is €99 and adds your own APIs and SQL databases, your own domain and your own identity provider. 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 · Claude

Connect Supabase to Claude. 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 Claude user in your team their own login, and lets Data, Support and Management query exactly the tables their role allows.

Start free Get a demo

Free for 2 servers, no card · Paid plans from €39 · EU-hosted

The problem

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.

Steps checked against the vendor documentation on 17 September 2026: Supabase MCP server · Personal access tokens · Management API introduction · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Who may do what

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 Claude user in your team gets exactly this.

Supabase runs on the free tier: two MCP servers for one person, no card. The roles, the identity per person and the masking above start at €39 a month, as soon as colleagues join. See the plans

What you get

Four checks between Claude 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.

Use cases

What people actually ask Claude 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.

Compare

Four ways to put Supabase into Claude.

	Native Supabase connector	Build it yourself	Enterprise gateways¹	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, paid from €39
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.

¹ MintMCP, MCP Manager, Pomerium

Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative

Also for

ChatGPT

Connect another system to Claude

All systems and clients →

FAQ

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 Claude?: One person with the right to add connectors in your Claude 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 Claude 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 Claude. 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 two MCP servers, forever, no card. Starter is €39 per month and adds roles, an identity of their own for every colleague, field masking and a 30-day audit. Team is €99 and adds your own APIs and SQL databases, your own domain and your own identity provider. 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 Claude, with rules.

One key in Loopthink, one login per person, one matrix that decides who may do what.