Connect Codex CLI
Add Supero to Codex CLI with url https://mcp.supero.dev/mcp in ~/.codex/config.toml, run codex mcp login supero, and build Supero apps from Codex.
- Codex CLI
- OpenAI Codex
- MCP
- OAuth
- config.toml
- codex mcp login
Overview
https://mcp.supero.dev/mcp over Streamable HTTP and signs you in through your browser (OAuth). No API key is needed.Tested
Add the server
~/.codex/config.toml:[mcp_servers.supero]
url = "https://mcp.supero.dev/mcp"- 1
Sign in
Run
codex mcp login supero. Your browser opens at Supero. Sign in, or create an account. No browser on that machine? Add--no-browserand paste the redirect URL back when asked. - 2
Allow
Codex identifies itself with a document hosted on chatgpt.com, so the approval page may name the app **ChatGPT**, or say "Supero hasn't verified this app" followed by 127.0.0.1. Either is expected. Pick where it may work (access options). Click Allow.
- 3
Use it
Start
codexand ask it to build an app; it calls the Supero tools.
Check the connection
build_whoami and answers with your workspace and access. Supero lists about 50 tools, with the build tools first.Your first app
Build a booking app for a dog grooming salon: customers pick a groomer and a time slot and pay a deposit; staff see the day's appointments.Use an API key instead (optional)
https://api.supero.dev/mcp/v1/messages with the key in the X-API-Key header; Two addresses, one set of tools explains why there are two addresses, and Use an API key instead covers creating a key in the console (Build via MCP). A project key can read, change and delete records in every tenant of its project. Never commit a key.[mcp_servers.supero]
url = "https://api.supero.dev/mcp/v1/messages"
env_http_headers = { "X-API-Key" = "SUPERO_API_KEY" }env_http_headers reads the header value from the SUPERO_API_KEY environment variable, so the key stays out of the file.Troubleshooting
- Use the URL exactly as
https://mcp.supero.dev/mcp, with no trailing slash. Some clients compare it with the server's published resource and stop if they differ. - "Too many registrations" (HTTP 429). Each new sign-in registers the tool with Supero. One IP address may register 10 times an hour (an IPv6 /64 network 20 times), and there is an overall hourly limit. Wait, then try again. A sign-in that already works is not affected.
- Signed in as the wrong account: remove the server, add it again, and use Switch account on the approval page.
- To disconnect, use Disconnect at app.supero.dev/oauth/connections, then remove the server from the tool's config.
- Changing your Supero password or email ends every assistant connection you signed in. Your projects and apps are not affected; sign in again from the tool.
- Codex keeps your sign-in in the OS keyring, or in
~/.codex/.credentials.json. If it expires, runcodex mcp login superoagain.
On this page