Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Synology MCP

by servosityversion 0.1.1i★ –iRuns on your computer
Registry nameio.github.Servosity/synology-mcp

Install

Overview

Description from the maker (original English)

Active Backup for Business jobs and storage health from every client Synology NAS, in one database

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Clinics & health
  • You need to fill in: SYNOLOGY_BASE_URL, SYNOLOGY_ACCOUNT, SYNOLOGY_PASSWORD, SYNOLOGY_DEVICE_ID, SYNOLOGY_OTP_CODE, SYNOLOGY_MCP_HTTP_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: 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_PROFILE

Values 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.

Values you fill in

  • SYNOLOGY_BASE_URL required env
    DSM address of the NAS with scheme and port, for example https://nas.acme.example:5001.
  • SYNOLOGY_ACCOUNT required env
    DSM account name used for the SYNO.API.Auth login.
  • SYNOLOGY_PASSWORD secret required env
    DSM account password; sent only in the login request, never written to disk.
  • SYNOLOGY_DEVICE_ID secret env
    Optional. Trusted-device token from an earlier two-factor login, used instead of a one-time code.
  • SYNOLOGY_OTP_CODE secret env
    Optional. One-time code for the first login of a two-factor account.
  • SYNOLOGY_TLS_FINGERPRINT env
    Optional. SHA-256 fingerprint of the NAS certificate to pin (DSM ships a self-signed certificate).
  • SYNOLOGY_SKIP_TLS_VERIFY env
    Optional. Set to 1 to skip certificate verification; prefer SYNOLOGY_TLS_FINGERPRINT.
  • SYNOLOGY_MCP_READ_ONLY env
    Optional. Blank, 0, false, no or off keeps every tool; any other value removes every write tool.
  • SYNOLOGY_MCP_HTTP_TOKEN secret env
    Bearer token of at least 32 characters that callers must present when the server runs with --transport http; not used by stdio.
  • SYNOLOGY_USER_AGENT env
    Optional. Overrides the User-Agent header the CLI sends to the NAS.
  • SYNOLOGY_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of NAS answers: reads go to the NAS live, the response cache is off, and sync and fleet sync refuse to run (so the fleet reports have no mirror to read). Leav…
  • PRINTING_PRESS_CLIENT_PROFILE env
    Not used by this connector (no tenant-gated client profiles); leave unset.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account servosity, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

  • More stars than 0% of the other 870 servers in this category
  • Published to the registry more recently than 94% of the other 870 servers in this category
  • Basic checks equal to or better than 100% of the other 870 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Synology MCP safe?

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.

What keys or codes does it need?

You need to fill in: SYNOLOGY_BASE_URL, SYNOLOGY_ACCOUNT, SYNOLOGY_PASSWORD, SYNOLOGY_DEVICE_ID, SYNOLOGY_OTP_CODE, SYNOLOGY_MCP_HTTP_TOKEN

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

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

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 6 days ago
Install

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago
Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago
Install

README from the maker

Open the README

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.

Synology + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

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.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

Your AI agentHow to install the Synology skill
Claude DesktopRun 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 CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste 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.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot 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 GeminiGemini 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.md directly *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

Download 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

Path A - paste one prompt into your AI agent (recommended)

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, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/synology/install.ps1 | iex. Then authenticate per the README and run synology-cli --help to 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/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
Upgrade 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/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.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, 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 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.

Install for Hermes

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.

Install for OpenClaw

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 the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

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.

What this skill does

Question your MSP keeps askingCommand
Is every client NAS OK? One row per NAS: backups, stale devices, storage, sync agesynology-cli fleet status

| Which Active Backup j

Only the beginning is shown; read the rest in the repo

Ask PopNx