Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
Fleet-wide backup health, failure triage and usage reports for every tenant on your Comet Server
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 2/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Comet Backup MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Comet Backup MCP or shows a Comet Backup MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Comet Backup MCP yet
Comet Backup MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Comet Backup MCP
B · Others in Clinics & health that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Comet Backup MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Comet Backup MCP
Cursor cannot connect Comet Backup MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Comet Backup MCP
VS Code cannot connect Comet Backup MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Comet Backup MCP
COMET_BACKUP_PASSWORD secret required envCOMET_BACKUP_SERVER required envCOMET_BACKUP_SESSION_KEY secret required envCOMET_BACKUP_USERNAME required envCOMET_BACKUP_BASE_URL envPRINTING_PRESS_CLIENT_PROFILE envCOMET_BACKUP_MCP_READ_ONLY envCOMET_BACKUP_NO_LOCAL_DATA envCOMET_BACKUP_USER_AGENT envCOMET_BACKUP_MCP_HTTP_TOKEN secret required envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
mcpb: …/comet-backup-mcp.mcpbBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
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 16, 2026
The registry name was verified with the GitHub account Servosity, which owns the repo
Code last changed yesterday
GitHub could not identify the licence type; open the file to check
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
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/servosity-comet-backup-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 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: COMET_BACKUP_PASSWORD, COMET_BACKUP_SESSION_KEY, COMET_BACKUP_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 yesterday, and the latest version (0.1.4) reached the registry 2 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: Medplum MCP, Mirobody, Codescene MCP Server, WHOOP — MissingMCP, Marrow
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Securely access and manage FHIR healthcare data stored in Medplum.
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
An MCP server that provides CodeScene Code Health analysis tools.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
| This one Comet Backup MCP | Medplum MCP | Mirobody | Codescene MCP Server | WHOOP — MissingMCP | Marrow | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 2/3 | 4/4 | 3/3 | 2/3 | 2/4 | 3/3 |
| License | NOASSERTION | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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 Comet Backup
API. Not affiliated with, endorsed by, or sponsored by Comet Licensing Ltd.
▶ 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
Fleet-wide backup health, failure triage and usage reports for every tenant on your Comet Server, plus the admin API calls an MSP uses day to day. 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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Comet Backup skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register comet-backup-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host comet-backup-mcp over HTTPS with COMET_BACKUP_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token. |
| 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 comet-backup-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run comet-backup-mcp --transport http with COMET_BACKUP_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not self-serve. Host comet-backup-mcp over HTTPS with COMET_BACKUP_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md. |
| Google Gemini | Gemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md. |
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 Comet Backup MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Comet Backup 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 comet-backup@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Comet Backup 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/comet-backup/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/comet-backup/install.ps1 | iex. Then authenticate per the README and runcomet-backup-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/comet-backup/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/comet-backup/install.sh)
The installer drops both comet-backup-cli (the CLI) and comet-backup-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
comet-backup-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/comet-backup/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/comet-backup/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 comet-backup@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 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.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/comet-backup --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/comet-backup --force
Hermes speaks MCP natively, so it can also use the comet-backup-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the comet-backup skill from https://github.com/servosity/msp-skills/tree/main/skills/comet-backup. The skill defines how its required CLI (
comet-backup-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.
Point the CLI at your Comet Server and a Comet admin account (a dedicated API admin with a long random password is best). For an admin that requires 2FA, set COMET_BACKUP_SESSION_KEY from Comet's session-start API instead of the password.
export COMET_BACKUP_SERVER=backup.example.com:8060
export COMET_BACKUP_USERNAME= export COMET_BACKUP_PASSWORD= comet-backup-cli doctor comet-backup-cli server version --json
Windows (PowerShell):
$env:COMET_BACKUP_SERVER = "backup.example.com:8060"
$env:COMET_BACKUP_USERNAME = " " $env:COMET_BACKUP_PASSWORD = " " comet-backup-cli doctor comet-backup-cli server version --json
doctor checks config and paths and makes one authenticated call to your server, so its credentials row reads healthy only when your login worked. The CLI connects over https and never sends the admin login over plain http: a Comet Server that only listens on plain http needs a TLS listener first. For a private certificate authority set COMET_BACKUP_CA_CERT to its PEM file.
| Question your MSP keeps asking | Command |
|---|---|
| Which backups failed, are overdue or never ran, across every tenant? | comet-backup-cli health --state failed,overdue,never --agent |
| Why did last night's backups fail? | comet-backup-cli triage --window 24h --group-by error --agent |
| Which tenants are near a storage, device or Microsoft 365 quota? | comet-backup-cli usage --over 80 --agent |
| Which offline devices stopped backing up but still cost money? | comet-backup-cli devices stale --older-than 7d --billable-only --agent |
| Which devices run an older Comet client than the server? | comet-backup-cli devices outdated --agent |
| What opened or resolved since yesterday? | comet-backup-cli snapshot then comet-backup-cli changes --only health --agent |
| Re-run the failed backups on devices that are online now | comet-backup-cli rerun-failed --window 24h (plan), then add --yes |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Comet Backup 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 protected items across all 60 tenants failed or have not run since Friday, and why".
This skill reads the whole server in a few bulk Comet calls and joins the answer locally. Compound commands like health, triage and usage join across tenants, devices, protected items, schedules, jobs and job logs in one pass - work a stateless API wrapper can't do - and the AI sees the answer, not the raw data. snapshot keeps each run's fleet state in a local SQLite store, so changes can say what opened or resolved since the last one.
Comet keeps every customer on one server, but its console and emailed job reports work one tenant and one job at a time. The backup that hurts most is the one that never reports a failure because it never ran: Magnus Box, a Comet-based backup provider, describes an MSP that lost a major client to an Exchange backup that had been failing silently for two months (source).
health --state failed,overdue,never lists every protected item that failed, is overdue against its own schedule, or never ran.-