Back to Blog

How to Connect ChatGPT to Supabase with MCP

Connect ChatGPT to Supabase via MCP: Developer Mode, service role vs anon/RLS, Synra endpoint, staging project first. Read-only gateway and table allowlists.

ChatGPT is where many non-engineers ask for numbers. Supabase is where the numbers live. Bridge today: CSV or a SQL editor screenshot.

With MCP, ChatGPT hits a read-only gateway; Synra talks to Supabase. ChatGPT path (Developer Mode) below. Claude: Connect Claude to Supabase. Cursor: Connect Cursor to Supabase. Any engine: Connect ChatGPT to Your Database.

Also: staging first, multi-tenant filters, where results go.

Service role vs anon

| Key | ChatGPT + Synra? | |-----|------------------| | anon | Usually too weak (RLS) | | service_role | Common — treat like a password | | SELECT-only Postgres user | Best when you can create one |

Empty answers with anon ≠ Synra broken. It’s often RLS.

Step 1 — Credentials

A — API path: Project Settings → API → Project URL + service_role (not anon).

B — Postgres URI: Settings → Database → URI → port 5432 (direct).

Prefer a staging Supabase project for the first connection.

Step 2 — Synra

  1. mcpserver.design → Connections → Add
  2. Supabase (A) or PostgreSQL (B)
  3. Name: supabase-staging
  4. Test → Save → table allowlist
  5. Copy MCP URL from Endpoints

Rotate if that URL leaks.

Step 3 — Developer Mode in ChatGPT

  1. ChatGPT web → profile → Settings
  2. Apps & Connectors → Advanced → Developer mode on
  3. Paid plan required; setup is web-first

Step 4 — Custom connector

  1. Create / Add custom connector
  2. Name: Synra Supabase staging
  3. Description: Read-only Supabase. Schema and SELECT for staging. Filter by org_id when asking about tenant data.
  4. MCP URL: Synra endpoint
  5. Auth: No authentication (token in URL)
  6. Create — confirm tools appear

Step 5 — Use in a chat

+ → Developer mode / your app → select Synra.

Try:

  • “List tables.”
  • “Describe profiles.”
  • “Signups last 7 days” (real table names after inspect)
  • Write attempt → should fail

Verify. Refresh the connector after schema changes.

Habit checklist

  • Staging project before production service role
  • Multi-tenant: put org_id in the prompt (guide)
  • Don’t commit the endpoint or service role
  • Support lookups: support + AI DB / chat vs admin UI

Credentials into Synra, Developer Mode on, known-answer question first.

7-day trial: mcpserver.design.

Related reading:

← Back to Blog