Skip to main content
Back to the Supabase MCP server

MCP Gateway · Codex

Supabase icon

Connect Supabase to Codex

Codex can test database changes on a Supabase development branch before they reach production. Engineering teams connect to Supabase through the Speakeasy MCP Gateway, where an admin picks per role which branch and project tools are allowed, and each call is written to an audit log.

Category
Data & analytics
Tools
29
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Supabase MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Supabase call inspected and logged.

Deploy on MCP Gateway

Set up

Add Supabase to Codex in 4 steps

  1. 01

    Add Supabase from the catalog

    An admin finds Supabase in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Supabase uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Supabase

    Give teams the mcp:connect scope on the Supabase server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Supabase to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Supabase from Codex

    The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Supabase needs its own OAuth grant, so each person connects it once. Until they do, Supabase calls fail while the rest of the gateway keeps working.

    From then on, Supabase's tools appear in Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Supabase

Try a migration on a branch

Codex gets the cost, confirms it with you, and creates a development branch with the main project's migrations, so your new migration runs there instead of on production.

get_costconfirm_costcreate_branch

Fix migration drift on a branch

When production has moved ahead, Codex checks the branch status and rebases it so newer production migrations run on the branch before you continue.

list_branchesrebase_branch

Merge once the checks pass

After your tests pass, Codex merges the branch's migrations and Edge Functions into production and then deletes the development branch.

merge_branchdelete_branch

Tools

29 tools

Each Supabase tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.

search_docs

Search the Supabase documentation using GraphQL. Must be a valid GraphQL query. You should default to calling this even if you think you already know the answer, since the documentation is always being updated.

list_organizations

Lists all organizations that the user is a member of.

get_organization

Gets details for an organization. Includes subscription plan.

list_projects

Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on.

get_project

Gets details for a Supabase project.

get_cost

Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each. Always repeat the cost to the user and confirm their understanding before proceeding.

See all 29 tools

Control

What Speakeasy can see and stop in Codex

The gateway covers every client the same way. The rest depends on what Codex exposes to Speakeasy.

Tool logs

Gateway

Every Supabase call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Supabase tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Supabase can reject a tool request before it reaches the server, or withhold a result from Codex. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Codex

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Can an admin keep Codex away from production merges?
Yes. Each Supabase tool can be allowed or denied per team at the gateway, so a role could create and reset branches without merge_branch. Agent hooks also send each tool call to Speakeasy, which allows or denies it before Codex runs it.
Can the device agent keep Codex's Supabase setup current?
Yes. The device agent keeps Codex's configuration in sync on managed laptops.
How do Codex users get Supabase?
An admin adds Supabase from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Supabase tools their access allows.
Are Supabase calls from Codex logged?
Yes. Supabase calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Supabase in other clients

AI everywhere.

Control here.