← All recipes

MCP Recipe

Explore a Supabase project before writing SQL

Influzer starter recipe: connect the Supabase MCP, inspect projects/tables first, then ask for read-only SQL with an explanation — before any writes or schema changes.

Data & Analytics
By Influzer Published 2026-11-19 Updated 2026-11-19 0 worked for me

MCP servers used

Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Desktop, Claude Code, ChatGPT

Prerequisites

  • Supabase remote MCP access to an org/project you own
  • Prefer a read-only mindset (and restricted roles) while exploring
  • Know which project/ref is safe to inspect

Required permissions

Supabase MCP can expose schema and run SQL depending on granted scopes. Keep production writes off until you review the query. Never paste service-role keys into chat.

Setup

1. Connect Supabase MCP

Add the Supabase remote MCP at https://mcp.supabase.com/mcp and complete OAuth for the org that owns the project you want to inspect.

2. Example mcp.json · json
{
  "mcpServers": {
    "supabase": {
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}
3. Schema first, then SELECT-only SQL · markdown
Using Supabase MCP, list my projects and inspect the schema for the primary app project (tables + key columns).
Then propose a read-only SQL query to answer: “How many new signups per day for the last 14 days?”
Explain the query before running any SELECT. Do not run INSERT/UPDATE/DELETE/DROP or change RLS policies.

Expected result

A table/column overview and a proposed read-only query with an explanation — no destructive statements.

Sample output

Project: acme-prod
Tables: profiles, subscriptions, events
Suggested SELECT: daily active users last 14 days grouped by plan…

Troubleshooting

  • Auth errors: reconnect https://mcp.supabase.com/mcp and re-authorize the org
  • Wrong project: name the project ref in the prompt
  • If the agent proposes DROP/UPDATE: stop and tighten the prompt to SELECT-only

Report an issue