Codex MCP Tips: Sentry and Supabase Setup

Codex MCP Tips cover image with Sentry and Supabase setup

If you are coming from Claude Code plugins, Codex can feel “lower level” at first.

The good news: you can get a very similar experience by wiring the same remote MCP servers directly in Codex.

Why it feels different

Claude Code plugins are packaged integrations.

Codex exposes MCP directly, so you configure servers yourself:

  • add server
  • login with OAuth
  • use tools

Same MCP server, different UX.

One-time OAuth support in Codex

For remote OAuth MCP servers, make sure rmcp_client is enabled.

In ~/.codex/config.toml:

[features]
rmcp_client = true

Then restart Codex.

Install Sentry MCP (Cloud)

codex mcp add sentry --url "https://mcp.sentry.dev/mcp"
codex mcp login sentry

Optional experimental endpoint used by Sentry’s .mcp.json:

codex mcp add sentry --url "https://mcp.sentry.dev/mcp/sentry/mcp-server?experimental=1"

Install Supabase MCP (Cloud)

A) Full power (closest to Claude plugin “manage everything”)

codex mcp add supabase --url "https://mcp.supabase.com/mcp"
codex mcp login supabase

B) Safer scoped mode (project + read-only)

codex mcp add supabase --url "https://mcp.supabase.com/mcp?project_ref=<YOUR_PROJECT_REF>&read_only=true"
codex mcp login supabase

If you want write operations, remove read_only=true.

If you want account-level and multi-project tools, do not scope by project_ref.

Verify setup

codex mcp list
codex mcp get sentry
codex mcp get supabase

Quick parity checklist (Claude Code -> Codex)

  1. Use the same MCP endpoint URL.
  2. Enable OAuth support (rmcp_client).
  3. Run codex mcp login <name>.
  4. Keep one server per integration (sentry, supabase) for clean mental model.

References