Supabase (local) logo

Supabase (local)

Beta

Supabase's MCP server manages projects and queries databases with a personal access token.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Supabase

How it works

Every agent request passes through Ferentin policy before it reaches Supabase (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @supabase/mcp-server-supabase.

Ferentin's endpoint agent finds Supabase (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Supabase (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Supabase (local)

Supabase's MCP server manages projects and queries databases with a personal access token.

Frequently asked about Supabase (local)

How do I connect Supabase (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Supabase (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Supabase (local) integration generally available?
The Supabase (local) integration is currently beta on Ferentin.