Integrations · Supabase
A Guild agent can provision Supabase projects, execute database queries, and manage auth configuration on your team’s behalf. Guild stores the personal access token server-side and injects it into every request without exposing it to the agent. Credential policies let you restrict which operations each agent may call, and every request is auditable through Guild’s credential proxy.
Book a demo
See how teams govern agents that use Supabase.
Talk to sales
Get access to Guild, then connect Supabase to your first agent.
What the Supabase integration exposes
The integration provides tools that cover project and organization management, database branching, SQL migration lifecycle, edge function deployment, secret management, auth service configuration, and backup and restore operations. Tools follow the naming convention supabase_v1_ and are imported from the guildai~supabase package. Use pick() to give an agent only the tools it needs.How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in your Guild account or organization. This page lists connected credentials and the integrations available to connect.
2
Connect your Supabase token
Click Connect, select supabase, and paste your Supabase personal access token into the API Key field. Guild sends it as a bearer token in the Authorization header on every request.
3
Import tools into your agent
Import SupabaseTools from @guildai-services/guildai~supabase and spread it into your agent’s tools object. Use pick() to include only the specific supabase_v1_ tools your agent requires.
Why Supabase access needs governing
Supabase tools can create or delete projects, apply and roll back SQL migrations, deploy edge functions, rotate API keys, and modify auth configuration. A credential scoped to the account grants wide reach by default. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request leaves Guild, limiting an agent to specific operations or HTTP methods without changing the underlying token. Credentials can be scoped to a workspace, a single member, or a dedicated agent so the right token is used in each context. Guild injects the token server-side after the policy check passes; agent code never sees it. If no rule allows a request, Guild denies it. You can delete the auto-created allow-all policy to enforce an explicit deny-by-default posture once your rules cover everything agents need.About the Supabase integration
Agents can create and manage Supabase projects, organizations, and database branches. They can run SQL migrations, deploy edge functions, and manage secrets and auth configuration. Access is established using a Supabase personal access token. The integration isguildai~supabase.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Supabase
In Guild, go to Access & setup > Credentials, click Connect, select supabase, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thesupabase_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~supabase:
All 170 tools
All 170 tools
Frequently asked questions
Can I limit an agent to read-only Supabase operations?
Can I limit an agent to read-only Supabase operations?
Yes. Write a credential policy that allows only operations matching patterns like supabase_v1_get_* and supabase_v1_list_*, and add a DENY rule for any mutating operations. Guild’s credential proxy enforces the rules before the request reaches Supabase.
Does the Supabase integration support webhook events?
Does the Supabase integration support webhook events?
No. The catalog entry for guildai~supabase lists no webhook events, so the integration does not receive event-driven triggers from Supabase.
Can different agents use different Supabase accounts?
Can different agents use different Supabase accounts?
Yes. You can connect a credential dedicated to a single agent from that agent’s page, or scope a credential to one workspace. Guild resolves credentials in order: grants and dedicated credentials take priority over workspace and account defaults.
How do I give an agent only some of the available tools?
How do I give an agent only some of the available tools?
Use the pick() helper from the Guild Agent SDK to select specific tools by name from SupabaseTools before spreading them into your agent’s tools object. The tools page documents pick() under selecting specific tools.
Put a governed agent on Supabase this week
Book a demo
See how teams govern agents that use Supabase.
Talk to sales
Get access to Guild, then connect Supabase to your first agent.