supabase-mcp-server MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

Three-tier query safety: safe (read), write (requires explicit write mode), destructive (requires extra confirmation)
Automatic versioned migrations for schema changes
Management API passthrough with auto-injected project ref
Auth Admin SDK — create/delete users, generate magic links
Logs + analytics across 9+ Supabase services

Demo en vivo

Cómo se ve en la práctica

supabase-2.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "supabase-2": {
      "command": "uvx",
      "args": [
        "supabase-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "supabase-2": {
      "command": "uvx",
      "args": [
        "supabase-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "supabase-2": {
      "command": "uvx",
      "args": [
        "supabase-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "supabase-2": {
      "command": "uvx",
      "args": [
        "supabase-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "supabase-2",
      "command": "uvx",
      "args": [
        "supabase-mcp-server"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

{
  "context_servers": {
    "supabase-2": {
      "command": {
        "path": "uvx",
        "args": [
          "supabase-mcp-server"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

claude mcp add supabase-2 -- uvx supabase-mcp-server

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: supabase-mcp-server

Ask questions about your app data in Supabase

👤 Founders, PMs on Supabase-backed apps ⏱ ~10 min beginner

Cuándo usarlo: You want usage / retention numbers without opening the Supabase SQL editor.

Requisitos previos

QUERY_API_KEY (free at thequery.dev) — Sign up, copy key
SUPABASE_PROJECT_REF + DB password — Supabase dashboard > Project Settings

Flujo

Stay in safe mode

Set mode to safe. How many users signed up last week?✓ Copiado

→ Read-only result; no mutation possible
Drill in

Of those, how many completed onboarding (have any row in profiles)?✓ Copiado

→ Retention-style number

Resultado: Quick answers with ironclad read-only guarantee.

Errores comunes

Switching to write mode for 'just this query' and forgetting to switch back — Tell Claude explicitly: 'Return to safe mode after this query.'

Make and track a schema change as a real migration

👤 Devs on Supabase ⏱ ~15 min intermediate

Cuándo usarlo: You need to add a column or index and want the change captured as a migration file, not an ad-hoc ALTER.

Requisitos previos

SUPABASE_ACCESS_TOKEN for Management API — Dashboard > Account > Access Tokens

Flujo

Switch to write mode

Set mode to write. Add column plan (text, default 'free') to users table.✓ Copiado

→ ALTER executed; migration file created
Review and commit

Show the generated migration file. I'll commit it to our repo.✓ Copiado

→ SQL file path + contents

Resultado: Schema change + tracked migration in one step.

Errores comunes

Migration conflicts with CI when team members also make changes — Coordinate via branch-per-migration; don't do this in main during team hours

Combinar con: github

Provision test users for dev/staging via Auth Admin SDK

👤 QA engineers, devs ⏱ ~10 min intermediate

Cuándo usarlo: You need 20 test accounts with specific metadata to exercise a feature.

Requisitos previos

SUPABASE_SERVICE_ROLE_KEY — Dashboard > API settings (keep secret!)

Flujo

Create users in bulk

Create 20 test users: [email protected] through [email protected], password 'Test12345!', with metadata {role: 'qa', plan: 'free'}.✓ Copiado

→ 20 user UUIDs returned
Generate magic links

For each, generate a magic sign-in link and save to /tmp/qa-users.tsv.✓ Copiado

→ TSV with email + link

Resultado: QA-ready accounts provisioned in under a minute.

Errores comunes

Service role key is god-mode — never put in prompt context in front of a user — Keep in env var; never echo

Combinar con: filesystem

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

supabase-2 + github

Generate migration file via MCP, commit via git MCP

Add a column via write mode, then commit the generated migration file with message 'feat: add users.plan'.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
execute_sql	query: str, mode: 'safe'\|'write'\|'destructive'	Main entry for arbitrary SQL, gated by current mode	1 DB query
set_mode	mode: 'safe'\|'write'\|'destructive'	Change safety tier; default is safe	free
management_api_request	path, method, body?	Manage project settings, extensions, buckets via Management API	1 API call
auth_admin_create_user	email, password?, user_metadata?	Provision users for testing or onboarding	1 Auth call
auth_admin_generate_link	user_id, type: 'magiclink'\|'recovery'	Get a sign-in or recovery URL for a user	1 Auth call
get_logs	service: 'api'\|'auth'\|'db'\|..., since, until	Debug by service	1 API call

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: Bounded by Supabase plan (DB connections, Management API rate limits)
Tokens por llamada: SQL results: depends on LIMIT; always cap
Monetario: Free (Apache 2.0). Supabase costs are your existing bill.
Consejo: Stay in safe mode by default. Only escalate when you explicitly intend to mutate.

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: SELECT for safe mode; INSERT/UPDATE for write; all for destructive

Almacenamiento de credenciales: Env vars. Service role key is especially sensitive.

Salida de datos: Queries go to your Supabase project; LLM sees the result rows

No conceder nunca: Service role key to anything that can be reached over untrusted transport

Maintainer has announced this MCP is no longer actively maintained — the official Supabase MCP (supabase-community/supabase-mcp) is now recommended.
Destructive mode has no extra wrapper beyond the mode toggle; the toggle itself is the confirmation.

Resolución de problemas

Errores comunes y soluciones

QUERY_API_KEY invalid

Regenerate at thequery.dev. Note: this is a separate service wrapping Supabase and requires its own signup.

Write tool refuses in safe mode

Call set_mode write first. Remember to set back to safe when done.

Transaction pool exhausted

Only transaction pooling is supported here. Reduce concurrency or upgrade Supabase plan.

Verificar: Supabase dashboard > DB > Connection Pooling

Alternativas

supabase-mcp-server vs otros

Alternativa	Cuándo usarla	Contrapartida
Official Supabase MCP	You're starting fresh — use the official one first	Maintained by Supabase; this community one has been deprecated by its author
postgres MCP	You only need SQL, not Auth/Management APIs	Read-only, universal; no Supabase-specific features
Neon MCP	You're on Neon, not Supabase	Adds DB branching for safe migration testing

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills