Database · 2 skills

Supabase MCP and Claude skills

Query your Supabase Postgres for signups and app metrics, read the security and performance advisors and logs, and report what changed in your project.

Connect Supabase to your agent (MCP)

  1. Supabase MCP server, Supabase's official remote server at https://mcp.supabase.com/mcp, signed in with OAuth. URL options narrow it: project_ref=<ref> limits it to one project, read_only=true runs every query as a read-only Postgres user, and features=database,debugging,docs loads only those tool groups. In Claude Code: claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp?project_ref=<ref>&read_only=true", then /mcp and Authenticate. In Codex, add the URL under [mcp_servers.supabase] in ~/.codex/config.toml and run codex mcp login supabase; in Cursor, put it under mcpServers in .cursor/mcp.json. Supabase is also in Claude's connector directory (docs).
  2. Unattended runs with a token. For CI or scheduled jobs, create a personal access token, store it in SUPABASE_ACCESS_TOKEN, and send it as Authorization: Bearer to the same project-scoped, read-only URL.
  3. Direct Postgres or the CLI. Connect with a read-only Postgres role and the connection string from the project's Connect panel, stored in DATABASE_URL, or run supabase link --project-ref <ref> and then the supabase inspect db commands.

Supabase's own advice for unattended routines: scope the server to one project, set read_only=true, limit features, and keep production out of reach unless the report needs it.

2 Supabase skills

What agents do with Supabase

A Supabase project is a Postgres database with auth, storage and edge functions around it, so most reports are SQL. Signups and activity come from auth.users (created_at, last_sign_in_at) and your own tables in public; uploads from storage.objects. The Supabase MCP server adds project tools: list_tables, execute_sql, get_advisors for the security and performance advisors (tables exposed without row level security, foreign keys without an index), logs per service, and edge function listings. From a terminal, the Supabase CLI's supabase inspect db commands (outliers, long-running-queries, table-record-counts, bloat) cover database health.

Founders and developers schedule daily signups and active users, new advisor warnings after a migration, the slowest queries of the week, errors in the API or auth logs, and table growth.

supabase.com

Your Supabase numbers, on one board with everything else

Skills are free to use with any agent. Briefkin is where their results land: one board for every report, number and question your agents send, with a ping when something needs you.

Free during the open beta. No card.