MCP and agent setup

The Cloud Noce CLI includes an MCP  server that communicates over stdio. It exposes projects, environments, services, domains, variables, logs, builds and releases as structured tools for AI assistants such as Claude Code, Cursor, Codex, GitHub Copilot, OpenCode, Grok, Devin, Pi, Gemini Antigravity and any MCP-compatible client. From your editor or terminal, ask your assistant to create or deploy a service, retrieve logs or configure environment variables. You do not need to give the assistant your account token directly: the server uses the CLI token saved by gerdoo login.

Setup steps

gerdoo setup agent

gerdoo setup agent flags

gerdoo setup agent [--agent claude-code|cursor|codex|copilot|opencode|devin|pi|grok|antigravity|print]
                   [--skill-only] [--no-skill] [--global]

Rerunning this command is safe: existing files are not overwritten; only their Cloud Noce configuration is updated.

Where is each tool configured?

For another MCP-compatible tool, or a tool configured through a web interface without local files, run gerdoo setup agent --agent print to print all four common formats. gerdoo mcp is a standard stdio server and works with any MCP client.

The gerdoo mcp command

If you prefer manual configuration, start the MCP server on standard input/output (stdio) with:

gerdoo mcp

Usually you do not run this directly; your assistant tool starts it as a subprocess. The gerdoo command must be on PATH in the environment where the assistant runs. On machines without a browser, such as CI or remote servers, set GERDOO_TOKEN instead of using gerdoo login.

Tools available to the assistant

The Cloud Noce MCP server provides more than 40 tools covering the Cloud Noce API:

• Account discovery: gerdoo_whoami returns the account email and a service summary: total count, counts by status and a short service list. It is a useful first call for understanding the account.
• Costs: gerdoo_get_pricing returns pay-as-you-go rates in toman (IRT): hourly CPU and RAM, monthly disk, outbound traffic and build minutes. Given a service size, it also estimates monthly cost. gerdoo_get_spending shows wallet balance, spending this month and the most expensive services.
• Projects and environments: listing, details and creation of projects and environments.
• Services: listing, details, creation from Docker images, local-folder deployment (gerdoo_deploy_service_source), configuration updates and start/stop/restart.
• Variables: both the simple env map and the typed build-time/secret store. All variable names are visible, but secret values and sensitive env values are hidden with [redacted].
• Domains: adding, verifying and deleting custom domains with their DNS records.
• Databases and managed add-ons: gerdoo_add_database creates an add-on (PostgreSQL, Redis, MinIO, RabbitMQ, MariaDB or MongoDB) and connects it to a service in one call, automatically injecting connection variables such as DATABASE_URL and REDIS_URL. Separate add-on creation, listing, binding and unbinding are also available.
• Marketplace templates: listing and details of templates and one-step deployment with gerdoo_deploy_template. Images and credentials always come from the platform catalog, and generated passwords are not returned to the assistant.
• Internal networking: gerdoo_get_service returns the service’s internal_address and other services in its project; gerdoo_list_services returns each service’s internal_host. Use these internal names to connect services to each other, rather than public addresses.
• Monitoring and troubleshooting: gerdoo_diagnose_service returns service status, container logs, the latest build and its logs, and a build-error explanation in one call. gerdoo_get_logs accepts level, grep, since and invert filters and reports the matching line count. gerdoo_exec executes a one-shot command in a running service container. Build and release listings and traffic metrics (gerdoo_get_metrics) are also available.
• Support tickets: create, read, reply to and close tickets (gerdoo_create_ticket and related tools) for issues that require platform support.
• Local-folder deployment: if a build fails, gerdoo_deploy_service_source includes the error analysis in its diagnosis field, so the assistant does not need extra calls to understand the cause.
• Sensitive operations: deleting services/projects, rollback and service suspension all require confirm: true and carry a destructive annotation in MCP so the client requests confirmation before execution.

Reference resources

Alongside tools, the MCP server publishes reference resources so assistants can read values instead of guessing:

The use-gerdoo skill

The use-gerdoo skill is procedural guidance installed with the CLI. It tells the assistant which tools to use for creating services, deploying the current folder, troubleshooting through logs and builds, and managing variables and domains. It also emphasizes that the assistant must explicitly request user confirmation before destructive operations.

Running gerdoo upgrade also updates the installed skill, unless you edited it yourself; in that case it is preserved and a message is shown.

# Install only the skill, without changing MCP configuration
gerdoo setup agent --skill-only
 
# Install globally for all projects
gerdoo setup agent --skill-only --global