Connect OpenAI Codex to Nodes2Cloud
The Codex CLI, IDE extension and app share config.toml.
OpenAI Codex talks to the Nodes2Cloud MCP server at https://api.nodes2cloud.com/mcp over Streamable HTTP. Once connected, your agent can read the node catalogue, write and check workflows, and request deploys that wait for your approval by default.
Sign in with your browser (recommended)
No token to copy. When OpenAI Codex first connects, your browser opens so you can sign in to Nodes2Cloud and approve access.
Add the server
codex mcp add nodes2cloud --url https://api.nodes2cloud.com/mcp
Sign in
codex mcp login nodes2cloud
Or add it to config.toml
toml- Global
~/.codex/config.toml - Project
.codex/config.toml
[mcp_servers.nodes2cloud] url = "https://api.nodes2cloud.com/mcp"
If the file already exists, add the nodes2cloud entry under mcp_servers and keep what is already there.
Use a Personal Access Token
For headless machines and CI, or if you would rather not sign in through the browser. Create one in the editor under Integrations → MCP server → Headless & CI Tokens, then Generate Token. Replace n2c_pat_YOUR_TOKEN below with it.
Treat the token like a password and keep it out of source control.
Add it to config.toml
toml- Global
~/.codex/config.toml
[mcp_servers.nodes2cloud]
url = "https://api.nodes2cloud.com/mcp"
http_headers = { Authorization = "Bearer n2c_pat_YOUR_TOKEN" }If the file already exists, add the nodes2cloud entry under mcp_servers and keep what is already there.
Or let the installer write it
The n2c-mcp installer writes the same config into OpenAI Codex's config file for you. Add --print to see it without writing anything.
npx -y n2c-mcp@latest install --client codex
Every flag is on the MCP setup page.
Good to know
- Using a token?
bearer_token_env_var = "N2C_API_KEY"keeps it out of the file.