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
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 Comet Backup MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Comet Backup MCP,或回答中出现 Comet Backup MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Comet Backup MCP
Comet Backup MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Comet Backup MCP 的应用
B · 诊所与健康 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Comet Backup MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Comet Backup MCP 的应用
Cursor 暂时无法连接 Comet Backup MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Comet Backup MCP 的应用
VS Code 暂时无法连接 Comet Backup MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Comet Backup MCP 的应用
COMET_BACKUP_PASSWORD 机密 必填 envCOMET_BACKUP_SERVER 必填 envCOMET_BACKUP_SESSION_KEY 机密 必填 envCOMET_BACKUP_USERNAME 必填 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 机密 必填 env说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月16日
注册名称已通过 GitHub 账户 Servosity 验证,该账户拥有此仓库
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/servosity-comet-backup-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:COMET_BACKUP_PASSWORD, COMET_BACKUP_SESSION_KEY, COMET_BACKUP_MCP_HTTP_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(0.1.4)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Medplum MCP, Mirobody, Codescene MCP Server, WHOOP — MissingMCP, Marrow
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
| 本项 Comet Backup MCP | Medplum MCP | Mirobody | Codescene MCP Server | WHOOP — MissingMCP | Marrow | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 2/3 | 4/4 | 3/3 | 2/3 | 2/4 | 3/3 |
| 许可证 | NOASSERTION | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.-