Mirobody
de thetahealth
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Se ejecuta en tu computadora★ 1408Apache-2.0Actualizado hace 5 días
Instalar
Cove Data Protection MCP
Resumen
Descripción del creador (original en inglés)
Fleet-wide Cove Data Protection backup health, billing, and storage trends from your terminal.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Clínicas y salud
- Debes completar: COVE_PARTNER, COVE_PASSWORD, COVE_USERNAME, PRINTING_PRESS_CLIENT_PROFILE, COVE_MCP_HTTP_TOKEN
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- Debes completar tú:
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_AGENT
Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Valores que debes completar
COVE_BASE_URLenvBase URL for the Cove Data Protection API. Leave the prefilled default unless your account uses a different regional or self-hosted host.- The full customer/partner string exactly as it appears in the Cove console dropdown, including the parenthesised email, e.g. 'Acme Corp (admin@example.com)'.
- API token issued with the Cove API user. Cove shows it once, at creation.
- Login name of the Cove API user (Cove console: Settings > API users). This is the API user's login, not your console email.
- Optional: binds the MCP server to an existing tenant-gated Printing Press client profile. Leave unset for a single-tenant install.
COVE_MCP_READ_ONLYenvOptional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.COVE_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
COVE_USER_AGENTenvOverrides the User-Agent the CLI sends on Cove requests.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Clínicas y saludi
- Más estrellas que el 0% de los otros 866 servidores de esta categoría
- Publicado en el registro más recientemente que el 70% de los otros 866 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 866 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Cove Data Protection MCP?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
Debes completar: COVE_PARTNER, COVE_PASSWORD, COVE_USERNAME, PRINTING_PRESS_CLIENT_PROFILE, COVE_MCP_HTTP_TOKEN
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.1.13) llegó al registro hace 10 días.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Mirobody, FHIR MCP Server, Google Health MCP
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
FHIR MCP Server
de wso2
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Se ejecuta en tu computadora★ 137Apache-2.0Actualizado hace 8 días
Instalar
Google Health MCP
de davidmosiah
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Se ejecuta en tu computadora★ 79MITActualizado hace 4 meses
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Cove Data Protection + 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 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.
Works with your agent
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.
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.
| 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.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Claude 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
Path A - paste one prompt into your AI agent (recommended)
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.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cove/install.ps1 | iexmacOS / 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 --versionUpgrade 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/cove/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cove/install.ps1 | iexClaude 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.
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/cove --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/cove --forceHermes speaks MCP natively, so it can also use the cove-mcp server directly - same install path, same env vars.
Install for OpenClaw
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.
Authenticate
See mcp-install.md for the credentials cove-cli needs.
What this skill does
| 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.
What makes this different
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.
The pain this closes
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 c
Solo se muestra el principio; lee el resto en el repo