Supabase

Supabase is the most popular open-source alternative to Firebase: managed Postgres, auth, storage, realtime, edge functions — all under one dashboard. The official connector exposes tools across 8 categories (Account, Database, Knowledge Base, Development, Edge Functions, Debugging, Branching, Storage), letting the agent read schemas, execute SQL, apply migrations, generate TypeScript types and deploy edge functions.

Ask "how many users signed up last week?" and it writes the SQL, runs it, returns the number. Ask "create a new table for invitation tracking" and it drafts the migration SQL — "SQL passed to this tool will be tracked within the database, so LLMs should use this for DDL operations", per the official README.

What you can ask

• "List the tables in the public schema with their columns and types — I need to understand the structure before doing an analysis."
• "How many active users did we have in the last 30 days, grouped by country."
• "Generate the migration to add a subscription_tier column to the users table with default 'free'."

Read-only mode (recommended for production)

The server supports an officially documented read-only mode: "all queries execute as a read-only Postgres user, disabling mutating tools entirely." It's the safe way to let the agent analyze production without risk of accidental UPDATEs/DROPs.

To enable it, pass --read-only to the server or use a read-only Postgres role in your project. Ideal for dashboards, analysis and debugging; only enable write mode in development projects.

What token you need

You need a Supabase Personal Access Token (PAT) — the server operates "under the context of your developer permissions" via this PAT. Different from the service_role or anon key of your project.

1. Go to supabase.com/dashboard/account/tokens.
2. Click "Generate new token". Name it something like "Terminal Sync — Claude".
3. Copy it (you only see it once) and paste it when the Lab asks for SUPABASE_ACCESS_TOKEN. Encrypted in your Keychain.

The PAT's scope is your Supabase account: the agent can see every project where you're owner/member. For critical production, we recommend a separate Supabase project as an "agent sandbox", or a dedicated account.