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

Open-source agent

# ConnectionOpenCode to Cloud Noce

Enables Cloud Noce as a local MCP server in OpenCode. The choice of model is still up to you. MCP retrieves current service information from Cloud Noce, so the agent can respond based on the actual state of your service.

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

terminal — oc

$ gerdoo setup agent --agent opencode

→ Wired gerdoo MCP into opencode.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 OpenCode connection

`gerdoo setup agent --agent opencode`

The third command saves the Cloud Noce connection in `opencode.json` . IfOpenCode 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.

«Show the services in this project and summarize each service's latest deployment status.»

«Check the structure of this repository and identify which components need separate services.»

## Access comes from your Gerdoo CLI session

OpenCode 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 guideDevin](/en/products/agents/devin)