Codex

Codex supports remote MCP servers over Streamable HTTP with OAuth.

1. Add the server

Run:

codex mcp add gummble --url https://mcp.gummble.com/mcp

Codex detects OAuth support and opens Gummble in your browser. Sign in, approve the consent screen, then return to Codex.

2. Verify

codex mcp list

gummble should show as logged in. Inside the Codex TUI you can also run /mcp and confirm the server is connected.

Then ask:

Before building this paywall, use Gummble MCP to find 5 mobile paywalls
with annual discount framing and summarize the layout patterns.

Codex should call Gummble tools before proposing UI or copy.

Manual config

If you prefer config files, paste this into ~/.codex/config.toml, or a trusted project's .codex/config.toml:

[mcp_servers.gummble]
url = "https://mcp.gummble.com/mcp"

Then authorize once:

codex mcp login gummble

For teams, commit project-level Codex config only when your repo already treats Codex project config as trusted. Keep user tokens in Codex's local auth store, not in source control.

Troubleshooting

• If Codex says the server is unavailable after credentials expire, re-run codex mcp login gummble.
• If auth opens but does not complete, check OAuth opens but fails.
• If tools appear but calls fail, check token/scope missing.