Synology MCP

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

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.

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

| Which Active Backup j