[All supported agents](/en/products/agents)

Software development agent

# ConnectionDevin to Cloud Noce

Configures Devin's access to deploy and troubleshoot Cloud Noce services within this project. MCP retrieves current service information from Cloud Noce, so the agent can respond based on the actual state of your service.

[ConnectionDevin](#setup)[Read the MCP guide](/en/support/docs/cli/agents)

terminal — dv

$ gerdoo setup agent --agent devin

→ Wired gerdoo MCP into .devin/mcp_config.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 | sh`

### Sign in to your Gerdoo account

`gerdoo login`

### Set up the Devin connection

`gerdoo setup agent --agent devin`

The third command saves the Cloud Noce connection in `.devin/mcp_config.json` . IfDevin 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.

«Fix this issue, deploy the updated version to the preview environment and check the result.»

«Investigate the failed deployment. Explain the cause first, then change the code or settings only if needed.»

## Access comes from your Gerdoo CLI session

Devin 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.

[Next guidePi](/en/products/agents/pi)