OpenAI agent
ConnectionCodex to Cloud Noce
Reads your project code and deploys it to Cloud Noce. If deployment fails, it finds the cause in the logs. MCP retrieves current service information from Cloud Noce, so the agent can respond based on the actual state of your service.
$ gerdoo setup agent --agent codex
→ Wired gerdoo MCP into .codex/config.toml
→ Installed use-gerdoo skill
✓ Ready to deploy.
Connect in three commands
Install the Gerdoo CLI and sign in first. The third command adds the MCP configuration and Gerdoo usage guide to your project.
Install the Gerdoo CLI
curl -fsSL https://get.gerdoo.cloud/install.sh | shSign in to your Gerdoo account
gerdoo loginSet up the Codex connection
gerdoo setup agent --agent codexThe third command saves the Cloud Noce connection in .codex/config.toml . IfCodex is open, restart it after setup.
Describe the outcome, not the tool
You do not need to know an API or MCP tool name. Clearly state the project and target environment. For production changes, ask the agent to explain its plan before running it.
«Deploy this project to Cloud Noce. If deployment fails, read the logs and fix the problem.»
«Investigate the latest failed deployment and explain the root cause with evidence from the logs.»
Access comes from your Gerdoo CLI session
Codex No separate token is needed. Secret values are not displayed in tool responses. For destructive actions, the agent must identify the resource and target environment and obtain your explicit approval.