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)
Active Backup for Business jobs and storage health from every client Synology NAS, in one database
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.
SYNOLOGY_BASE_URL, SYNOLOGY_ACCOUNT, SYNOLOGY_PASSWORD, SYNOLOGY_DEVICE_ID, SYNOLOGY_OTP_CODE, SYNOLOGY_TLS_FINGERPRINT, SYNOLOGY_SKIP_TLS_VERIFY, SYNOLOGY_MCP_READ_ONLY, SYNOLOGY_MCP_HTTP_TOKEN, SYNOLOGY_USER_AGENT, SYNOLOGY_NO_LOCAL_DATA, PRINTING_PRESS_CLIENT_PROFILEValues 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.
SYNOLOGY_TLS_FINGERPRINT envSYNOLOGY_SKIP_TLS_VERIFY envSYNOLOGY_MCP_READ_ONLY envSYNOLOGY_USER_AGENT envSYNOLOGY_NO_LOCAL_DATA envPRINTING_PRESS_CLIENT_PROFILE 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: SYNOLOGY_BASE_URL, SYNOLOGY_ACCOUNT, SYNOLOGY_PASSWORD, SYNOLOGY_DEVICE_ID, SYNOLOGY_OTP_CODE, SYNOLOGY_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.1) reached the registry yesterday.
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 Synology
API. Not affiliated with, endorsed by, or sponsored by Synology Inc.
▶ 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
Every client NAS's Active Backup for Business jobs and storage health, mirrored into one local SQLite database and checked with one command. 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 Synology skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register synology-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host synology-mcp over HTTPS with SYNOLOGY_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 synology-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run synology-mcp --transport http with SYNOLOGY_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 synology-mcp over HTTPS with SYNOLOGY_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 Synology MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Synology 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 synology@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Synology 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/synology/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/synology/install.ps1 | iex. Then authenticate per the README and runsynology-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/synology/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/synology/install.sh)
The installer drops both synology-cli (the CLI) and synology-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
synology-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/synology/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/synology/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 synology@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/synology --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/synology --force
Hermes speaks MCP natively, so it can also use the synology-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the synology skill from https://github.com/servosity/msp-skills/tree/main/skills/synology. The skill defines how its required CLI (
synology-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.
DSM has no API keys: the CLI logs in with a DSM account in the administrators group (Active Backup for Business management and Storage Manager calls need administrator rights; Active Backup's own Operator and Manager delegation roles are not tested with this CLI). Use a dedicated account per client NAS. Passwords are read from environment variables and never written to disk. The address must be https:// (port 5001 by default): plain http://, this machine included, is refused before the password is sent.
One NAS - macOS / Linux:
export SYNOLOGY_BASE_URL=https://192.168.1.50:5001 SYNOLOGY_ACCOUNT=<account> SYNOLOGY_PASSWORD=<password>
synology-cli auth login
Windows (PowerShell):
$env:SYNOLOGY_BASE_URL = "https://192.168.1.50:5001"; $env:SYNOLOGY_ACCOUNT = "<account>"; $env:SYNOLOGY_PASSWORD = "<password>"
synology-cli auth login
Every client NAS - register each one, then sync them all. The login for a NAS named acme comes from SYNOLOGY_ACME_ACCOUNT and SYNOLOGY_ACME_PASSWORD (or the prefix you pass with --env-prefix). macOS / Linux:
export SYNOLOGY_ACME_ACCOUNT=<account> SYNOLOGY_ACME_PASSWORD=<password>
Windows (PowerShell):
$env:SYNOLOGY_ACME_ACCOUNT = "<account>"; $env:SYNOLOGY_ACME_PASSWORD = "<password>"
Then, in either shell:
synology-cli fleet add acme --url https://nas.acme.example:5001 --pin-cert
synology-cli fleet add acme --url https://nas.acme.example:5001 --client "Acme Corp" --tls-fingerprint --check synology-cli fleet sync synology-cli fleet status
The fleet reports (fleet status, fleet health, fleet capacity, abb failures, abb stale, abb unprotected, abb device, abb trend, abb change-rate) read every registered NAS from the local mirror, and abb triage takes --nas . The other live commands (abb tasks, abb backup, hyperbackup, storage, system, user, group and the rest) talk to the one NAS in SYNOLOGY_BASE_URL, so point it at a client's NAS (with that NAS's SYNOLOGY_ACCOUNT and SYNOLOGY_PASSWORD) before asking about it.
Most NAS units serve DSM's self-signed certificate. --pin-cert only displays: it prints the SHA-256 fingerprint of the certificate the address presents, where to compare it in DSM (Control Panel > Security > Certificate) and the --tls-fingerprint command that pins it, and saves nothing and sends no request (it refuses --check). Pin with --tls-fingerprint only after that value matches DSM, and the CLI then trusts exactly that certificate; for a single NAS set SYNOLOGY_TLS_FINGERPRINT instead. --check logs in once and reports whether Active Backup for Business is installed.
Two-factor accounts: add a fresh code to the first login only - SYNOLOGY_OTP_CODE for one NAS, SYNOLOGY_ACME_OTP_CODE for a fleet NAS ($env:SYNOLOGY_OTP_CODE = "123456" in PowerShell). DSM returns a trusted-device token, which the CLI keeps with that NAS's cached session and sends on later logins.
Every login first checks that the address answers as DSM's WebAPI, so an address that is not a DSM (a router, a web page) never receives the password; another Synology would, so check each address you register. synology-cli doctor checks config and paths, confirms SYNOLOGY_BASE_URL answers as a DSM WebAPI, then logs in and makes one authenticated read, so it reports the login as valid, rejected (wrong account or password) or needing a two-factor code; fleet add --check does the same for a fleet NAS.
| Question your MSP keeps asking | Command |
|---|---|
| Is every client NAS OK? One row per NAS: backups, stale devices, storage, sync age | synology-cli fleet status |
| Which Active Backup j
Only the beginning is shown; read the rest in the repo