# Synology NAS [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/cmeans/mcp-synology  
**GitHub Stars:** 12  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/synology-nas

## Description
MCP server for Synology NAS — browse files, monitor health, and automate operations

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "synology-nas": {
    "command": "uvx",
    "args": ["mcp-synology"]
  }
}
```

## Documentation

## What Synology NAS does

The Synology NAS MCP server connects an MCP client to a Synology NAS through the DSM API. Its tools cover three areas: File Station, System, and Download Station. File Station provides file and shared-folder operations, System reports NAS information and current resource use, and Download Station manages download tasks when that module is enabled.

File Station includes read and write permission tiers. Read operations can list shares and files, search, inspect file details, calculate directory size, view the recycle bin, and download files. Write operations can create folders, rename, copy, move, delete, restore recycle-bin items, upload files, and handle file tasks.

The System module provides model, firmware version, memory, temperature, uptime, CPU, memory, disk I/O, and network information. Basic system information is available to all users; resource usage requires an administrator account.

## How it works

The Synology NAS MCP server translates MCP tool calls into requests to DSM. Access is governed by the configured module and permission level, along with the Synology account used by the server. File Station and System are available through the standard setup path, while Download Station is opt-in.

Download Station exposes read tools for listing downloads, retrieving task details and statistics, viewing configuration, and checking the schedule. Write tools can create, delete, pause, resume, and edit downloads, change download configuration, and set the schedule. The Download Station package must be installed on the NAS before these calls can succeed.

## Setup and configuration

The package provides an `mcp-synology setup` command that configures File Station. Configuration is stored under `~/.config/mcp-synology/config.yaml`, or in a per-NAS file when Multi-NAS configuration is used. The `mcp-synology check --config <file>` command validates YAML and configuration values and checks whether login still works.

To enable Download Station, add its module under the existing `modules:` section and choose `permission: read` or `permission: write`. Restart the MCP client after changing configuration because the server reads its configuration only at startup.

Torrent and NZB uploads use a local file path. By default, local files must come from the Downloads folder. Additional permitted folders can be configured with `allowed_local_paths`.

## Tools and capabilities

- Browse shares, directories, and files.
- Search files and inspect file metadata or directory size.
- Upload, download, copy, move, rename, delete, and restore files.
- Read NAS identity, firmware, temperature, uptime, and memory details.
- Read live CPU, memory, disk, and network usage with an administrator account.
- Manage Download Station tasks, settings, and schedules when enabled.

## Limitations and notes

A folder download is saved as DSM's ZIP archive, using the folder name or a supplied filename. Downloading an entire shared folder is refused because DSM does not provide it as a single download.

Non-admin Download Station users need the application privilege in DSM. They can view and manage only their own tasks, change their own default destination, and cannot change NAS-wide speed limits. An administrator is required for weekly schedules and limited-speed rates, although non-admin users can still toggle the schedule.

A Download Station user may need to set a default destination before tasks can start. The `set_download_config` tool can set that destination for the user. A task created with an explicit destination may be accepted but warned that it will not start until the required setup is complete.

The repository documents testing against DSM 7.1, 7.2.2, 7.3.2, and 7.4.1. Users upgrading from the older `synology-mcp` package can use the provided migration script to move configuration, state, keyring credentials, and Claude Desktop settings.

_Full upstream README: https://allmcps.com/mcp/synology-nas/readme_