Ask questions about Supabase
A read-only managed agent for Supabase project diagnostics.
- chat
- supabase-answerer
- supabase-readonly
supabase-answerer-pool
- supabase-answerer-model
supabase
What this template gives you
Interface
A chat window, in your browser
Use the included interface to send a request to this template.
Gateway
supabase-readonly gateway
This template sends its requests through supabase-readonly gateway, where its access rules and limits apply.
Model
supabase-answerer-model
This template uses supabase-answerer-model through the supabase-answerer-pool pool.
Usage
Hand this template to an AI agent to set up this template
Node.js and npm to run npx.
Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.
Docker Compose to run the companion app locally.
- 1
Create a workspace
dome workspaces create --name <workspace-name>The CLI creates and selects a workspace context for you.
- 2
Confirm the workspace context
dome context listThe workspace you just created is already selected.
- 3
Pull the template
npx @domesystems/templates pull dome-systems/ai-agent-for-supabase@0.1.0 --dir ai-agent-for-supabaseDownloads this immutable release and verifies its digest.
- 4
Run the template
npx @domesystems/templates up --dir ai-agent-for-supabaseImports it into Dome and starts the companion app.
Dome import variables
npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.
Required values
DOME_IMPORT_VAR_anthropic_api_key
Setup guide
Follow this template's setup guidance for agent variables and upstream connections.
# Configure Supabase
- `anthropic_api_key`: enter the Anthropic key used by this agent's model.
This template uses the hosted Supabase MCP server's browser OAuth flow with
Dynamic Client Registration. It does **not** need a Supabase OAuth client ID,
client secret, or manually registered callback URL.
- Import the template, then select **Connect** on the Supabase tool connection.
- Sign in with a least-privileged user that can access only an isolated,
non-production test project.
- Confirm that the authorization is for the intended project before accepting
the browser consent screen.
- The authorization requests read-only organization, project, database,
analytics, Edge Function, environment, and Storage access. It does not
request `secrets:read` or any write scope.
- Refresh the tool catalog after the connection succeeds, then run one
read-only test against known non-production data.
The endpoint includes `read_only=true`; do not connect sensitive production
data without a separate review. The upstream server's available tools and
project access are still determined by the authorized Supabase identity.Runtime environment
These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.
No .env.example is included in this release.Agent instructions
Inspect the selected Supabase project, schema, logs, and read-only diagnostics. Do
not run writes, migrations, secrets operations, deployments, or configuration changes.