Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
Fleet-wide Cove Data Protection backup health, billing, and storage trends from your terminal.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
COVE_BASE_URL, COVE_PARTNER, COVE_PASSWORD, COVE_USERNAME, PRINTING_PRESS_CLIENT_PROFILE, COVE_MCP_READ_ONLY, COVE_NO_LOCAL_DATA, COVE_MCP_HTTP_TOKEN, COVE_USER_AGENTValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
COVE_BASE_URL envCOVE_MCP_READ_ONLY envCOVE_NO_LOCAL_DATA envCOVE_USER_AGENT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: COVE_PARTNER, COVE_PASSWORD, COVE_USERNAME, PRINTING_PRESS_CLIENT_PROFILE, COVE_MCP_HTTP_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.13) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Unofficial. Community-built Claude Code Skill and MCP server for the Cove Data Protection
API. Not affiliated with, endorsed by, or sponsored by N-able.
▶ 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
The first CLI and MCP server for Cove Data Protection: fleet-wide backup health, billing usage, and storage trends from a terminal, with the local history the vendor console doesn't keep. 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 Cove Data Protection skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register cove-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add cove-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 cove-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs cove-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list. Setup steps: mcp-install.md.
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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companioncove-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setCOVE_CLI_PATHto an existing binary). Details: #331.
Download Cove Data Protection MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Cove Data Protection 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 cove@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Cove Data Protection 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/cove/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cove/install.ps1 | iex. Then authenticate per the README and runcove-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/cove/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cove/install.sh)
The installer drops both cove-cli (the CLI) and cove-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
cove-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/cove/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cove/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 cove@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/cove --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/cove --force
Hermes speaks MCP natively, so it can also use the cove-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the cove skill from https://github.com/servosity/msp-skills/tree/main/skills/cove. The skill defines how its required CLI (
cove-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.
See mcp-install.md for the credentials cove-cli needs.
| Question your MSP keeps asking | Command |
|---|---|
| Which devices failed their last backup since yesterday? | cove-cli devices failures --since 24h --json |
| Which devices have no successful backup in 3 days? | cove-cli devices stale --days 3 --json |
| What's the fleet health rollup, broken down per customer? | cove-cli fleet health --by partner --json |
| Which devices and customers grew storage fastest this week? | cove-cli storage growth --since 7d --json |
| What's the month-end billing usage per device, codes decoded? | cove-cli billing usage --csv |
| Which device SKUs changed since last month? | cove-cli billing changes --json |
| What backup statuses flipped since my last snapshot? | cove-cli devices changes --since 7d --json |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Cove Data Protection 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 how many devices failed or went stale across all 40 customers last night, with the F00 status codes already decoded to names.
This skill sweeps the whole partner tree in one command and snapshots Cove into a local SQLite mirror with full-text search. Aggregate questions become one local sweep: instant, offline, and the AI sees the answer, not the raw data. Compound commands like fleet health --by partner and storage growth --since 7d join across devices, customers, and timestamped snapshots - trend work a stateless API wrapper can't do because the console keeps no history at all.
MSPs running Cove Data Protection (the N-able backup platform, formerly SolarWinds Backup) keep hitting the same wall: the backup.management console scopes to one customer at a time and keeps no history. Threads on r/msp and the MSPGeek community ask the same questions over and over - "how do I get one cross-customer list of every failed backup?" and "how do I trend storage when the dashboard only shows today's number?" In the console the answer is always: click into each customer, eyeball the dashboard, repeat tomorrow. A silently stale device - one whose last status reads fine but hasn't actually succeeded in days - stays invisible until a restore fails.
What this skill does about it:
cove-cli devices failures --since 24h --agent - the morning ticket queue: every failed, aborted, or never-started device across the whole fleet, status codes decoded.cove-cli devices stale --days 3 --json - the silently stale devices the last-status view hides, ranked worst-first.cove-cli fleet health --by partner --json - the single-pane rollup (healthy, failed, stale, never-run) with a per-customer breakdown.cove-cli storage growth --since 7d --agent - which devices and cOnly the beginning is shown; read the rest in the repo