Backup Radar MCP

Backup Radar + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

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

API. Not affiliated with, endorsed by, or sponsored by ScalePad Software Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Also from Servosity. Backup & DR is Servosity's own field - the first-party Servosity connector brings this same fleet-wide, local-mirror approach (fleet attention, stale backups, restores, QBR reporting) to Servosity Backup and DR.

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

Every Backup Radar v3 and v2 endpoint plus a local store that finds the backups nobody is watching. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. 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):

The ChatGPT desktop app runs backup-radar-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, which msp-skills does not support yet (see mcp-install.md). If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

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 Backup Radar MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Backup Radar release on the releases page.)

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 backup-radar@msp-skills

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

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

Install the Backup Radar 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/backup-radar/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/backup-radar/install.ps1 | iex. Then authenticate per the README and run backup-radar-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/backup-radar/install.ps1 | iex

macOS / Linux:

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

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

Verify:

backup-radar-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/backup-radar/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/backup-radar/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 backup-radar@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, 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 ChatGPT desktop app. 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/backup-radar --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/backup-radar --force

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

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the backup-radar skill from https://github.com/servosity/msp-skills/tree/main/skills/backup-radar. The skill defines how its required CLI (backup-radar-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

Set the credentials the CLI needs (the v3 key from the ScalePad API tab, the v2 key from Backup Radar; either alone is enough for its own commands):

# macOS / Linux

BACKUP_RADAR_API_KEY= BACKUP_RADAR_V2_API_KEY= backup-radar-cli doctor

# Windows PowerShell

$env:BACKUP_RADAR_API_KEY = " "; $env:BACKUP_RADAR_V2_API_KEY = " "; backup-radar-cli doctor

doctor checks config, paths and API reachability, then probes each configured key against the API (GET /clients/health for the ScalePad v3 key, GET /backups/overview for the Backup Radar v2 key) and reports valid, rejected or not verified per key (credentials, credentials_v2). The process exits 0 even when a row says ERROR; pass --fail-on error in scripts. Either key alone is enough for its own commands.

What this skill does

Every analysis command reads the local mirror that backup-radar-cli sync fills from whichever keys you set, and each one says which collections it skipped because they were never synced. The mirror is scoped to the credentials that filled it (the v3 key, and the v2 key when one was set), so run the analysis commands with the same BACKUP_RADAR_API_KEY (environment or auth set-token) and the same BACKUP_RADAR_V2_API_KEY setting that sync used.

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Backup Radar integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which of our 400 backups has been silent for a week with no ticket, and which client's compliance rate fell last quarter".

This skill syncs Backup Radar into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like check, unwatched and scorecard join across the ScalePad v3 client-health and device history and t