All clients
Codex
Codex speaks MCP over streamable HTTP, add the server to `~/.codex/config.toml` and Codex handles the rest.
Setup
Codex
Loading setup…
- Who it’s for
- Developers running OpenAI’s Codex CLI as their coding agent.
- Compatibility
- Codex stores MCP configuration in `~/.codex/config.toml` (user scope) or `.codex/config.toml` at the root of a trusted project. Streamable HTTP transport is supported via a `url` key on the `[mcp_servers.*]` table; OAuth and bearer-token auth are both supported.
- Verify the connection
- After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.
Troubleshooting
- After editing `config.toml`, restart your Codex session, the MCP server list is read at startup.
- If the OAuth handshake fails, check the trust-store for your project; Codex requires the parent project to be marked trusted for project-scoped MCP servers.
- Codex stores OAuth tokens in your OS keychain; on a fresh machine, you re-authenticate the first time you invoke a tool.