Cloudback MCP Server

Product Introduction

1. Definition: The Cloudback MCP Server is an official Model Context Protocol (MCP) server application developed by Myrtle Labs. It functions as a specialized AI-driven tool and integration bridge, designed to allow AI-powered coding assistants and editors—such as Claude Code, Claude Desktop, Cursor, and VS Code with extensions—to directly manage and automate the backup infrastructure of software development platforms.
2. Core Value Proposition: The core value proposition is to eliminate manual, repetitive dashboard interactions and custom scripting for backup management. It provides a natural language interface to control complex backup operations across multiple platforms, enabling users to configure, schedule, and manage hundreds of backup definitions simultaneously through simple, conversational prompts. This represents a shift toward AI-powered DevOps (AIOps) for data protection.

Main Features

1. Unified Backup Configuration & Bulk Management via Natural Language:

   • How it works: The MCP server acts as a conduit between a user's natural language commands in an AI client and the Cloudback backup API. A user can issue a command like, "Adjust the retention policy for all Linear workspace backups to 90 days and set the schedule to daily at 2 AM UTC." The server parses this intent, translates it into the appropriate API calls, and applies the change across all 300+ related backup definitions in a single batch operation.
   • Technologies Used: Model Context Protocol (MCP), Cloudback REST API, Docker containerization (image: myrtlelabs/cloudback-mcp).

2. Cross-Platform Support for Centralized Management:

   • How it works: The server provides a single point of control for backup definitions across disparate software development and project management ecosystems. Through the same MCP client interface, a user can manage backups for GitHub repositories, GitLab projects, Azure DevOps organizations, and Linear workspaces. This eliminates the need to context-switch between different native backup tools or dashboards for each platform.
   • Technologies Used: Integration with platform-specific APIs (GitHub, GitLab, Azure DevOps, Linear) via the Cloudback platform as an intermediary.

3. Direct Control Over Storage and Security Policies:

   • How it works: Beyond scheduling, the server allows conversational management of critical security and compliance parameters. Users can instruct the AI to "link all new backups to our Wasabi S3-compatible bucket and enable AES-256 encryption for a specific backup set," or "generate an audit log report for all backup activities in the last week." This brings storage destination control, encryption key management (including Bring Your Own Key - BYOK), and compliance reporting into the same natural language workflow.
   • Technologies Used: Integration with cloud storage APIs (AWS S3, Azure Blob Storage, Google Cloud Storage, Wasabi, OneDrive), RSA Lockbox for customer-managed encryption, and audit log generation.

Problems Solved

1. Pain Point: Configuration Drift and Operational Overhead at Scale. Manually configuring or updating backup policies (schedules, retention, storage locations) for hundreds or thousands of repositories via web dashboards is time-consuming, error-prone, and creates a significant operational burden. It also leads to configuration drift, where backups are not uniformly compliant with organizational policy.
2. Target Audience:
   • DevOps and Platform Engineers: Responsible for automating infrastructure and ensuring system resilience.
   • Security and Compliance Officers: Need to enforce data protection policies, retention schedules, and audit trails across all development assets.
   • Technical Leads and Full-Stack Developers: Who manage multiple codebases across platforms and need efficient disaster recovery setup without leaving their development environment.
3. Use Cases:
   • Emergency Policy Update: A compliance officer needs to immediately extend the retention period for all active project backups to 12 months due to a new regulation. They issue one command via Claude Desktop.
   • Migration and Onboarding: When a company onboards a new GitHub organization with 50 repositories, a DevOps engineer can use a single prompt in VS Code to create and configure backups for all repositories to the company's designated Azure Storage account.
   • Audit Preparation: An admin quickly requests an activity summary for all backup operations from the past quarter through a chat interface, generating the necessary data for an audit without navigating multiple admin panels.

Unique Advantages

1. Differentiation: Unlike traditional backup management that relies on "point-and-click" dashboards or writing and maintaining custom automation scripts (which require coding and API knowledge), the Cloudback MCP Server offers a third paradigm: conversational infrastructure management. It is fundamentally different from competitors that offer only a SaaS dashboard or CLI tools. It integrates directly into the developer's existing AI-augmented workflow, reducing context switching.
2. Key Innovation: The key innovation is the application of the Model Context Protocol (MCP) to the domain of data protection and backup management. This protocol standardizes how AI models interact with external tools and data. By building an MCP server specifically for backup operations, Cloudback enables a seamless, secure, and context-aware connection between AI coding assistants and the complex backup infrastructure API, making natural language control both possible and practical for critical operations.

Frequently Asked Questions (FAQ)

1. How do I get started with the Cloudback MCP Server? To begin using the Cloudback MCP Server, you first need an active Cloudback account. Then, configure your MCP client (such as Claude Desktop, Cursor, or a compatible VS Code extension) to connect to the Docker container image myrtlelabs/cloudback-mcp. Once connected, you can start managing your GitHub, GitLab, Azure DevOps, or Linear backups using natural language commands directly in your IDE or chat interface.
2. Is the Cloudback MCP Server a replacement for the Cloudback web dashboard? No, the MCP Server is a powerful complementary interface, not a full replacement. The web dashboard remains essential for initial account setup, user management, and visual reporting. The MCP Server excels at bulk configuration changes, automated scripting via AI, and integrating backup management into developer workflows, providing a faster method for complex, repetitive, or large-scale operations.
3. Which backup platforms does the Cloudback MCP Server support for management? The Cloudback MCP Server provides management capabilities for backups covering four major platforms: GitHub, GitLab, Azure DevOps, and Linear. You can create, update, and manage backup definitions, schedules, retention policies, and storage configurations for repositories and workspaces across all these supported platforms through the same natural language interface.
4. Can I use the MCP Server to manage backups to my own cloud storage (BYOK)? Yes, a core feature is managing backups with Bring Your Own Storage (BYOS) and Bring Your Own Key (BYOK). Through conversational commands, you can instruct the MCP Server to link backup definitions to your own AWS, Azure, Google Cloud, Wasabi, or OneDrive storage accounts and manage the associated RSA encryption keys via the RSA Lockbox, maintaining full control over your data location and security.