Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Every Backup Radar v3 and v2 endpoint plus a local store that finds the backups nobody is watching.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
BACKUP_RADAR_API_KEY, BACKUP_RADAR_V2_API_KEY, BACKUP_RADAR_BASE_URL, BACKUP_RADAR_MCP_READ_ONLY, BACKUP_RADAR_NO_LOCAL_DATA, BACKUP_RADAR_MCP_HTTP_TOKEN, BACKUP_RADAR_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILEAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Die .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
Trag die leeren Werte ein, bevor du ihn startest.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
BACKUP_RADAR_BASE_URL envBACKUP_RADAR_MCP_READ_ONLY envBACKUP_RADAR_NO_LOCAL_DATA envBACKUP_RADAR_USER_AGENT envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto servosity bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: BACKUP_RADAR_API_KEY, BACKUP_RADAR_V2_API_KEY, BACKUP_RADAR_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.3) kam vorgestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du MCPB auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Rystic
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Backup Radar skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register backup-radar-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add backup-radar-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add backup-radar-mcp to mcp.json under the servers key, then pick Agent mode. |
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.
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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *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.
.mcpbDownload 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
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/backup-radar/install.ps1 | iex. Then authenticate per the README and runbackup-radar-cli --helpto explore.
The same prompt works in any agent that can run shell.
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
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.
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.
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.
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 theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
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.
| Question your MSP keeps asking | Command |
|---|---|
| Which backups are failing or silent today, new or ongoing, and how many tickets are open on each? | backup-radar-cli check --agent |
| Which backups is nobody watching: inactive, unmapped to ScalePad, failing with no ticket, no PSA company, or warnings counted as success? | backup-radar-cli unwatched --agent |
| What is one client's backup compliance rate over 90 days, with the weekly trend and the five worst devices? | backup-radar-cli scorecard "Acme Dental" --days 90 --agent |
| Rank every client by backup compliance, worst first | backup-radar-cli scorecard --days 90 --agent |
| What happened to one device's backups day by day this month, with tickets, tags and notes? | backup-radar-cli timeline "DC01" --days 30 --agent |
| Which backups have had no result in 45 days and could be retired, with a dry-run retire body for each one it can pin? | backup-radar-cli stale --days 45 --agent |
| Does the backup vendor protect devices that Backup Radar does not monitor, or the reverse? | backup-radar-cli coverage diff --devices vendor-devices.json --agent |
| Push results from a backup tool Backup Radar cannot parse, validated and batched under the 10,000-result limit | backup-radar-cli push --from results.csv --dry-run |
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.
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
Nur der Anfang wird gezeigt; den Rest findest du im Repo