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)은 그저께 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 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.-