CloudAlly MCP

CloudAlly + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the CloudAlly

API. Not affiliated with, endorsed by, or sponsored by CloudAlly or OpenText.

CloudAlly is a trademark of OpenText Corporation.

Comparing backup vendors? One of our MSP partners told us, "My guys now spend a tenth of the time on backups." Fixing is included in every Servosity co-managed backup plan, and our engineers tell you what they did. See how co-managed backup works

Restore or download every CloudAlly mailbox as it stood on a past date, read each mailbox's backup history, and find failing backups across every customer. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

For ChatGPT, run cloudally-mcp --transport http and serve it over HTTPS behind an authenticating proxy that signs ChatGPT in with OAuth and adds the Authorization: Bearer header the server requires (ChatGPT cannot send a fixed bearer token, so a bare tunnel gets HTTP 401) - no bridge package is needed. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download CloudAlly MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every CloudAlly release on the releases page.)

CloudAlly still needs one sign-in from a terminal: the extension calls cloudally-cli for its tools and reads its saved token, so also install the CLI (Path B below) and run cloudally-cli auth login --partner (or auth login for one company) once.

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install cloudally@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the CloudAlly Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cloudally/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cloudally/install.ps1 | iex. Then authenticate per the README and run cloudally-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cloudally/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cloudally/install.sh)

The installer drops both cloudally-cli (the CLI) and cloudally-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

cloudally-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cloudally/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cloudally/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update cloudally@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/cloudally --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/cloudally --force

Hermes speaks MCP natively, so it can also use the cloudally-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the cloudally skill from https://github.com/servosity/msp-skills/tree/main/skills/cloudally. The skill defines how its required CLI (cloudally-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Create an API application in the CloudAlly partner portal (Integrations > REST API), then sign in once with your partner login and check it:

export CLOUDALLY_CLIENT_ID=<client id>

export CLOUDALLY_CLIENT_SECRET= export CLOUDALLY_PARTNER_EMAIL= cloudally-cli auth login --partner --password-stdin < password-file cloudally-cli doctor

Windows (PowerShell):

$env:CLOUDALLY_CLIENT_ID = "<client id>"

$env:CLOUDALLY_CLIENT_SECRET = " " $env:CLOUDALLY_PARTNER_EMAIL = " " Get-Content password-file | cloudally-cli auth login --partner --password-stdin cloudally-cli doctor

Windows PowerShell 5.1 sends piped text as ASCII. For a password with non-ASCII characters, run $OutputEncoding = [System.Text.UTF8Encoding]::new($false) first, or set $env:CLOUDALLY_PARTNER_PASSWORD and run cloudally-cli auth login --partner.

$env: lasts only for that window; use setx or System Properties > Environment Variables to keep the key pair.

auth login --partner saves the access and refresh tokens (never printed) and the CLI refreshes them on its own. The partner login reaches every customer and is what the distributor-* and reseller-* commands, auth use-account, past backup dates, downloads and backup health need. To work inside one company only, set CLOUDALLY_EMAIL and CLOUDALLY_PASSWORD and run cloudally-cli auth login instead. doctor then makes one authenticated read (GET /v2/user), so it reports whether the token actually works, not just whether one is set.

What this skill does

| What are this month's