Docs

Supabase

Connect a Supabase project to Agenties so the orchestrator can inspect tables and run SQL — tracked alongside code changes, issues, and audit logs inside the same project flow.

How to connect

1.Open Settings for the project.
2.Go to Integrations → Supabase.
3.Enter your Supabase Project URL (e.g. https://your-ref.supabase.co).
4.Enter your service role key (found in Project Settings → API).
5.Save — credentials are stored in your OS keychain.
Warning:Agenties uses the service role key, not the anon key. The service role key bypasses Row Level Security and has full database access. Only connect projects where you own and understand the data. Never expose the service role key in client-side code.

MCP tools

ToolParametersDescription
supabase_list_tables-List tables available in the configured Supabase project.
supabase_execute_sqlsqlExecute raw SQL on the configured Supabase project and return query results.
Warning:SQL runs with full service-role access. Start with read-only inspection queries and use explicit permission gates for migrations, deletes, updates, or production-impacting operations.

Recommended workflow

StepWhat the agent should do
1 - InspectCall supabase_list_tables to understand the schema surface.
2 - Read firstUse supabase_execute_sql for narrow SELECT queries before changing anything.
3 - Plan changesDescribe the intended mutation or migration and the rollback path.
4 - Execute with approvalRun writes only after the user or orchestrator has accepted the risk for that operation.

Common use cases

Use caseExample
Schema discoveryFind tables and columns before wiring a feature to project data.
Data debuggingInspect failed records, stuck jobs, or inconsistent project state.
Operational reportsGenerate small summaries from project tables for artifacts or chat briefings.
Migration verificationRun SELECT queries before and after a migration to confirm expected row counts.