MCP serverValidated

Supabase MCP — your database, schema, and logs

The official Supabase server: inspect schema, run queries, and read logs against your project — so backend debugging happens against the real database shape instead of guesses.

io.github.supabase/mcp-server-supabaseOfficial docs →

A vetted listing, not an install — add the config to your MCP client yourself. CoSquared never writes MCP config.

Why this one

First-party and project-scoped, with a read-only flag — the safe default for letting an agent see (not mutate) production-shaped data.

How to use it

  1. 1Always start with --read-only and a dev project
  2. 2Use a personal access token you can revoke independently

Client config

Placeholders only — bring your own values

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase@latest",
        "--read-only",
        "--project-ref",
        "YOUR_PROJECT_REF"
      ],
      "env": {
        "SUPABASE_ACCESS_TOKEN": "YOUR_ACCESS_TOKEN"
      }
    }
  }
}

Security notes

The access token is account-scoped — treat it like a password and prefer a dedicated token. Without --read-only the agent can run mutating SQL; keep it read-only unless you are supervising every call. Query results (real rows) enter model context.