Cloudback MCP Backup Coverage Review

Cloudback MCP Backup Coverage Review

Review Cloudback backup coverage through the Cloudback MCP Docker server, identify backup definitions with disabled or failed backups, ask for human approval before configuration changes, and notify the engineering team through Slack.

What this workflow does

1. cloudbackConfig collects the full Platform::Account::ApiKey account entry and the review scope
2. cloudbackOpsAgent starts myrtlelabs/cloudback-mcp over stdio and uses Cloudback MCP tools for backup, storage, schedule, and account review
3. The Agent treats read/list/view actions as safe, but asks for human approval before update, create, delete, storage, schedule, account-setting, or bulk-change MCP calls
4. notifyCloudbackReview posts the review URL and proposed action to Slack when HITL approval is needed
5. cloudbackAuditReport returns the final reviewed backup report and decision metadata for traceability

Use cases

• Backup coverage reviews for GitHub, Linear, GitLab, or Azure DevOps accounts
• Detecting backup definitions with disabled or failed backups across supported platforms
• Safe ops automation where an agent can recommend changes but humans approve writes
• Demoing Docker-based stdio MCP servers inside Heym

MCP setup

Cloudback expects OpsApi__BaseUrl and one or more OpsApi__Account__N values. It does not read CLOUDBACK_API_KEY. Each connected account needs its own Operations API key generated from the Cloudback dashboard at app.cloudback.it/apikeys. There is no single global key across every organization, group, or workspace.

Because this template launches the MCP server through Docker, the values must be forwarded into the container with docker run -e flags:

{
  "args": [
    "run",
    "--platform",
    "linux/amd64",
    "-i",
    "--rm",
    "--pull=always",
    "-e",
    "OpsApi__BaseUrl=https://app.cloudback.it/",
    "-e",
    "OpsApi__Account__1",
    "myrtlelabs/cloudback-mcp"
  ],
  "env": {
    "OpsApi__Account__1": "$cloudbackConfig.body.accountEntry"
  }
}

Enter the account entry as the full Platform::Account::ApiKey string, for example GitHub::your-org::your-cloudback-api-key. Supported platforms include GitHub, AzureDevOps, GitLab, and Linear.

For multiple accounts, add separate entries such as OpsApi__Account__1=GitHub::org-a::key-for-org-a and OpsApi__Account__2=GitLab::group-b::key-for-group-b. Each key should be generated for that specific account in Cloudback.

Setup

Connect an LLM credential in cloudbackOpsAgent, add a Slack credential in notifyCloudbackReview, and replace the placeholder accountEntry value with a key from app.cloudback.it/apikeys before running. The Cloudback MCP server is pulled with Docker, so the Heym runtime needs Docker access.