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.

Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. 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

Supabase in Claude. In five minutes.

Connect Supabase in Loopthink, paste one URL into Claude, ask. Hosted in the EU, every call logged.

Start free See the steps

Free for 2 connectors, no card · Pro €19 · EU-hosted

How to connect

Three steps. The third one is asking.

1
Connect Supabase in Loopthink
Scoped personal access token, read-only, one project.
2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"How many rows landed in orders yesterday, broken down by country?" Every answer comes from your data, every call is logged.

Start free

Show all steps

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.
4
Open Settings, then Connectors, then Add, and choose Add custom connector. The dialog asks for exactly two things: a name your colleagues will recognise, and the MCP server URL, which is your Loopthink connector URL.
5
Continue, and Claude reads the server before it asks you anything. It detects that the server signs people in, and that it can register itself, so the sign-in and OAuth-client options are already chosen. Nothing has to be typed there, no client id, no secret, no request header.
6
Add it, then each team member opens Connectors, clicks Connect on it and signs in once with their own account. In a chat the connector appears in the + menu. Toggle it on and ask.

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

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

Why Loopthink

Supabase has an MCP server. Why Loopthink?

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 runs hosted and gives Claude a URL. Every colleague signs in with their own account and sees only what you ticked.

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 it cost?: Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. 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.

When colleagues join

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 connectors for one person, no card. Roles, a login for every colleague and field masking start at €19 a month with Pro. See the plans