Smart code editor
ConnectionCursor to Cloud Noce
Connects Cursor's built-in agent to live project and service data from Cloud Noce, so its answers reflect the actual state of your infrastructure. 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 cursor
→ Wired gerdoo MCP into .cursor/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 Cursor connection
gerdoo setup agent --agent cursorThe third command saves the Cloud Noce connection in .cursor/mcp.json . IfCursor 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 this code repository, find its service in Cloud Noce and deploy the new version.»
«Read the service's runtime logs and find the cause of the database connection error.»
Access comes from your Gerdoo CLI session
Cursor 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.