Supabase

Live

Attach Supabase projects as MCP servers in Builder terminals — connect your own Supabase account with a personal access token and give each Builder project the database it works against, read-only by default.

Register →

Capabilities

  • BYO personal access token (tenant vault); many accounts per workspace
  • One database attached per Builder project
  • Read-only by default; writes are an explicit choice
  • Exposed to the terminal agent as an MCP server

Common Use Cases

  • Let the terminal agent inspect a client's schema while it builds
  • Keep production databases read-only for agent sessions

How to Connect Supabase

  1. 01

    Open Settings → Integrations

    From your Zyan Admin workspace, open Settings → Integrations and pick the Supabase tile. The workspace owner or an admin connects it once for the whole workspace.

  2. 02

    Paste a personal access token

    Create the token in your Supabase account and paste it; Zyan checks it against Supabase and stores it in your workspace vault, never a platform key.

  3. 03

    Attach a database to a project

    In a Builder project's Supabase area, add one of the account's projects; it stays read-only unless you loosen it.

  4. 04

    Use it in the terminal

    Sessions with the database grant see the project as an MCP server; switch it off per project at any time.

Related — Workflow & Automation

← All integrations