Outside data
Two tools, integrations and integration_sql, let the agent see the Supabase project you connected to the app, read its tables and run SQL on it; full tool set only.
You connect Supabase in the dashboard, under Connections › Data sources. The agent never receives or asks for Supabase keys. The app’s own database stays the default store; Supabase is for data you already keep there.
integrations
Shows the connection state and the data structure.
- Parameters:
project. - Returns:
supabase(the connection state) and, when it is active,tableswith each table’s columns. When nothing is connected, no project is picked or the authorization expired,nextsays what to do in the dashboard. - When the agent calls it: before writing code that reads Supabase data.
Once connected, the backend reads data through manh/supabase (supabase, supabaseFetch). manh.run sets the secrets SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY and SUPABASE_SECRET_KEY.
integration_sql
Runs SQL (Postgres) on the connected Supabase project.
- Parameters:
project.sql: the statement, up to 100,000 characters.write:trueallows writes and schema changes (creating and altering tables, indexes, RLS policies). Defaultfalse, read-only.
- Returns:
writeand the statement’s result. - When the agent calls it: to look at sample data, or to add tables and columns the app needs.
This is your real data. The agent asks you before deleting data or dropping anything, and prefers adding over changing what exists.
Next steps
- Data on Supabase: reading and writing Supabase from the backend.
- Database: the app’s own database.
- Agent tools: the two tool sets.