Rockslab MCP · Rockslab docs

Give your AI agent the cabinet. The Rockslab MCP server has a tool for nearly everything you can do in the cabinet, acting as you, with your role.

What it is

An MCP server at https://cloud-api.rockslab.io/mcp with around 140 tools named rockslab_*: list clusters, build one, follow an operation, deploy an app, read limits and invoices, write to support. Each tool calls the same handler the cabinet's buttons call — same rules, same roles, same audit log. The agent is not a back door; it is you, typing faster.

Connect

Mint an API token, then add the server to your agent. For Claude Code:

claude mcp add --transport http rockslab https://cloud-api.rockslab.io/mcp \
  --header 'Authorization: Bearer ${ROCKSLAB_TOKEN}'

Keep the token in an environment variable or a secret store, not in the file itself.

First calls

rockslab_get_me — which organization the token acts in, and with which role.
https://cloud-api.rockslab.io/mcp/llms.txt — the server's own index: every tool with what it does and what it costs, generated from the server so it is never out of date.
The skills — short guides written for agents: build-a-cluster, connect-a-cloud, deploy-an-app, limits, read-an-operation, schedule-a-cluster and more. They are MCP resources (skill://<name>/SKILL.md) and plain files under /mcp/skills/.

How agents should behave

The server tells your agent this itself, but it is worth knowing:

Long verbs return an operation. Builds, installs and syncs answer at once; the agent follows the operation with rockslab_get_operation.
Poll every 30–60 seconds. Every call costs agent tokens; a loop that asks every second burns the budget and finishes no sooner.
Destructive tools need confirm: true. Deleting a cluster also needs its exact name. A good agent asks you first; a well-raised one says what it is about to delete.
Some things stay with people: inviting, billing, the plan and kubeconfigs. The tools for them do not exist, on purpose.

Seeing what an agent did

Activity › Audit log lists every call under the person whose token made it. rockslab_get_my_token_usage shows what the budget went on, tool by tool.

Your Hetzner project, too

This server manages Rockslab — clusters, apps, domains. To let an agent manage the Hetzner project itself (servers, volumes, firewalls…), use the Hetzner console MCP.