mcp-synology
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SYNOLOGY_HOST | Yes | NAS IP address or hostname | |
| SYNOLOGY_PORT | No | DSM port. The port you use to open DSM in a browser: 5001 for HTTPS by default, or 5000 for HTTP. If you changed it, it's under Control Panel → Login Portal → DSM. Defaults to 5001, or 5000 without HTTPS. | 5001 |
| SYNOLOGY_USER | Yes | DSM username | |
| SYNOLOGY_HTTPS | No | Set to 0 to connect over plain HTTP. | 1 |
| SYNOLOGY_PASSWORD | Yes | DSM password | |
| SYNOLOGY_PERMISSION | No | Permission level: 'read' (default, look only, nothing on the NAS is changed) or 'write' (also pause and resume Cloud Sync connections). Tools above your chosen level are hidden from the assistant entirely. A 'destructive' level is reserved for future tools that delete data or shut the NAS down; it requires both SYNOLOGY_PERMISSION=destructive and SYNOLOGY_ALLOW_DESTRUCTIVE=1. | read |
| SYNOLOGY_VERIFY_SSL | No | Set to 0 to accept a self-signed certificate. This skips the certificate check; only do that on a network you trust. | 1 |
| SYNOLOGY_ALLOW_DESTRUCTIVE | No | Set to 1 along with SYNOLOGY_PERMISSION=destructive to enable the reserved 'destructive' permission level. No tools use it yet. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_infoA | NAS hardware and DSM version: model, CPU, RAM, uptime, temperature, crash/upgrade flags, USB devices. |
| system_utilizationA | Live load: CPU %, load average, memory, per-disk and per-network-interface throughput. |
| storage_statusB | Disk and volume health: volume usage and free space; drive model, status, SMART, temperature. |
| cloudsync_statusA | Cloud Sync overview (Dropbox, Google Drive, OneDrive, S3, ...): per connection status, files left, cloud quota, sync tasks, throughput and ETA. Start here for "is the sync done / how long left". |
| cloudsync_activityB | Cloud Sync live activity: files transferring right now (with progress) and the latest completed changes. |
| cloudsync_logsA | Cloud Sync log history for one connection, newest first: what was uploaded, downloaded or deleted, and errors. Filter by action or keyword. |
| taskscheduler_tasksA | DSM Task Scheduler: every scheduled and event-triggered task (including root's) with schedule, next run and the last run's result and duration. Use to confirm a nightly job (e.g. a backup) succeeded. |
| taskscheduler_runsA | Run history of one scheduled task, newest first: start time, duration and exit result. Also shows the task's action (the command, for script tasks). |
| logcenter_logsB | DSM Log Center, newest first. system: hardware, disk/RAID, network link, updates, services. connection: sign-ins and failed logins (DSM, SSH, SMB, NFS...). smb: SMB file operations (who, IP, path). |
| dsm_notificationsB | DSM desktop notifications, newest first (e.g. Security Advisor, package and DSM updates). Titles are DSM message ids; params are their values. |
| network_configA | Network setup (static configuration): hostname, default gateway, DNS servers, and each interface's IP/subnet, MAC, link status, negotiated speed/duplex and MTU. Live throughput is in system_utilization. |
| packagesA | Installed packages with version, running/stopped status and available updates (new version, and whether it is a security release), checked against Package Center's catalogue and any third-party feeds configured there. Packages in neither (system components, manual installs) show update_to "not in catalogue". |
| hardware_powerB | Disk hibernation timers (internal and USB disks), hibernation debug settings, recent disk wake-ups from the system log, fan mode, power-on/off schedule, restart after power loss, Wake-on-LAN and UPS status. DSM does not report whether a disk is currently spun down. |
| filestation_list_sharesA | Shared folders (the top-level paths on the NAS), grouped by free space on their volume. |
| filestation_listB | List a folder's contents with size and modified time. |
| filestation_infoC | Size, modified time and real volume path for specific files or folders. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools target clearly distinct resources: system_utilization vs system_info vs storage_status are well separated, and taskscheduler_tasks vs taskscheduler_runs are distinct. The main risk is the cloudsync trio (status/activity/logs) and the filestation pair (list_shares vs list), though the descriptions resolve these by scope (overview vs live vs history; top-level vs folder contents).
All names use lowercase snake_case with a consistent <domain>_<subject> pattern (cloudsync_status, taskscheduler_runs, filestation_list_shares). Minor deviation: 'packages' has no domain prefix and verb-style varies (status/utilization/info), but overall it is predictable and readable.
16 tools is slightly heavy but justified by the breadth of NAS domains covered (cloud sync, storage, system, scheduler, logs, network, packages, power, file station). Each tool maps to a real distinct area, so nothing is obviously redundant or trivial.
The surface is thorough for monitoring/inspection but read-only: no tools to create/update scheduled tasks, manage cloud sync connections, or perform file operations (upload/download/delete) despite filestation listing tools existing. Coverage of the observation domain is good, but write/lifecycle operations are notable gaps.