Anthropic agent
ConnectionClaude Code to Cloud Noce
Accesses Cloud Noce services from your coding environment and follows the deployment through to completion. 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 claude-code
→ Wired gerdoo MCP into .mcp.json
→ 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 Claude Code connection
gerdoo setup agent --agent claude-codeThe third command saves the Cloud Noce connection in .mcp.json . IfClaude Code 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.
«Check the production service's status. If there is an error, find the cause before making any changes.»
«Create a service for this project, set the required variables and give me its URL.»
Access comes from your Gerdoo CLI session
Claude Code 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.