Codex's setup is two commands, and the second question most people ask, "do I need a client id for this," has a genuinely simple answer: no.

Connect it

Add the server:

codex mcp add develosaur --url https://mcp.develosaur.com/v1/user/mcp

Then sign in:

codex mcp login develosaur

That opens the browser consent screen, you approve it with your existing account, and the connection is live.

Or write the config by hand

If you would rather edit the file directly, ~/.codex/config.toml takes the same server as a plain entry:

[mcp_servers.develosaur]
url = "https://mcp.develosaur.com/v1/user/mcp"

Either path ends at the same sign-in.

Why there is no client id to register first

The gateway supports dynamic client registration, so Codex registers itself the moment you run the login command. There is no separate step where you request credentials from a dashboard, copy a client id, and paste it into a config file before any of this works. The address is the only thing you need up front.

If login gets stuck

Codex reporting that the server needs login again usually just means the sign-in did not complete; run codex mcp login develosaur a second time. A sign-in page that loops back means the email link opened in a different browser than the one that started the request, so finish it in the same one; a corporate proxy or VPN blocking the callback usually clears itself on a retry off that network.

Full setup, troubleshooting and FAQ live on the Codex integration page. The sign-in itself is the same OAuth-only flow covered in why Develosaur has no API keys to paste; more of these are on the blog.