💾 Synology MCP Server

A Model Context Protocol (MCP) server for Synology NAS devices. Enables AI assistants to manage files and downloads through secure authentication and session management.
Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से

A Model Context Protocol (MCP) server for Synology NAS devices. Enables AI assistants to manage files and downloads through secure authentication and session management.
💾 Model Context Protocol (MCP) server for Synology NAS - Enables AI assistants (Claude, Cursor, Continue) to manage files, downloads, and system operations through secure API integration. Features Docker deployment, auto-authentication, and comprehensive file system tools.
🌟 NEW: Unified server supports both Claude/Cursor (stdio) and Xiaozhi (WebSocket) simultaneously!
No need to clone the repository — install the package directly from PyPI:
# With pip
pip install mcp-server-synology
# Or with pipx (isolated environment)
pipx install mcp-server-synology
# Or with uv
uv tool install mcp-server-synology
This installs two equivalent commands: synology-mcp and mcp-server-synology.
For MCP clients, uvx is the simplest option — it downloads and caches the package automatically, no manual install or local clone required:
{
"mcpServers": {
"synology": {
"command": "uvx",
"args": ["mcp-server-synology"]
}
}
}
Configuration lives outside the package, so it works the same as a source checkout: create ~/.config/synology-mcp/settings.json as described in Configuration Options.
# Clone repository
git clone https://github.com/atom2ueki/mcp-server-synology.git
cd mcp-server-synology
# Create environment file
cp env.example .env
Basic Configuration (Claude/Cursor only):
# Required: Synology NAS connection
SYNOLOGY_URL=http://192.168.1.100:5000
SYNOLOGY_USERNAME=your_username
SYNOLOGY_PASSWORD=your_password
# Optional: Auto-login on startup
AUTO_LOGIN=true
VERIFY_SSL=false
Extended Configuration (Both Claude/Cursor + Xiaozhi):
# Required: Synology NAS connection
SYNOLOGY_URL=http://192.168.1.100:5000
SYNOLOGY_USERNAME=your_username
SYNOLOGY_PASSWORD=your_password
# Optional: Auto-login on startup
AUTO_LOGIN=true
VERIFY_SSL=false
# Enable Xiaozhi support
ENABLE_XIAOZHI=true
XIAOZHI_TOKEN=your_xiaozhi_token_here
XIAOZHI_MCP_ENDPOINT=wss://api.xiaozhi.me/mcp/
.env is read at run time, never baked into the image — docker-compose.yml
injects its entries as container environment variables via env_file, so the
file itself is not present inside the container. It is optional: if you
configure NASes with settings.json instead (recommended), you can skip this
file entirely.
One simple command supports both modes:
# Claude/Cursor only mode (default if ENABLE_XIAOZHI not set)
docker-compose up -d
# Both Claude/Cursor + Xiaozhi mode (if ENABLE_XIAOZHI=true in .env)
docker-compose up -d
# Build and run
docker-compose up -d --build
# Install the package and its dependencies (from PyPI, or from a clone with 'pip install .')
pip install mcp-server-synology
# Run with environment control
python main.py
The examples below use Docker with a local clone of this repository. If you installed from PyPI, use the uvx configuration from Install from PyPI instead — it works for Claude Desktop, Cursor, Continue and Codeium alike, with no local paths to adjust.
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"synology": {
"command": "docker-compose",
"args": [
"-f", "/path/to/your/mcp-server-synology/docker-compose.yml",
"run", "--rm", "synology-mcp"
],
"cwd": "/path/to/your/mcp-server-synology"
}
}
}
Add to your Cursor MCP settings:
{
"mcpServers": {
"synology": {
"command": "docker-compose",
"args": [
"-f", "/path/to/your/mcp-server-synology/docker-compose.yml",
"run", "--rm", "synology-mcp"
],
"cwd": "/path/to/your/mcp-server-synology"
}
}
}
Add to your Continue configuration (.continue/config.json):
{
"mcpServers": {
"synology": {
"command": "docker-compose",
"args": [
"-f", "/path/to/your/mcp-server-synology/docker-compose.yml",
"run", "--rm", "synology-mcp"
],
"cwd": "/path/to/your/mcp-server-synology"
}
}
}
For Codeium's MCP support:
{
"mcpServers": {
"synology": {
"command": "docker-compose",
"args": [
"-f", "/path/to/your/mcp-server-synology/docker-compose.yml",
"run", "--rm", "synology-mcp"
],
"cwd": "/path/to/your/mcp-server-synology"
}
}
}
If you prefer not to use Docker:
{
"mcpServers": {
"synology": {
"command": "python",
"args": ["main.py"],
"cwd": "/path/to/your/mcp-server-synology",
"env": {
"SYNOLOGY_URL": "http://192.168.1.100:5000",
"SYNOLOGY_USERNAME": "your_username",
"SYNOLOGY_PASSWORD": "your_password",
"AUTO_LOGIN": "true",
"ENABLE_XIAOZHI": "false"
}
}
}
}
By default the server speaks stdio, which means the MCP client has to spawn the process locally (or via a bridge such as SSH/docker exec). For setups where the NAS is remote (different machine from where Claude/Cursor runs), set MCP_HTTP=true and the server serves native Streamable HTTP from uvicorn in the same process — no mcp-proxy sidecar and no separate /sse endpoint. This makes it consumable by any MCP client that supports URL-based connectors — exactly like ha-mcp or other "remote" MCP servers.
[Claude Desktop / Cursor / ...]
│
│ HTTPS (URL connector)
▼
[Reverse proxy: DSM / Nginx / Traefik / Caddy]
│ (TLS termination + auth)
│ HTTP localhost:8765
▼
[Docker container]
└─ python main.py
└─ uvicorn → Streamable HTTP at /mcp
pyproject.toml: mcp>=2.0.0 ships starlette,
uvicorn, and sse-starlette, so the same image serves both stdio and
Streamable HTTP — no extra build arg or separate requirements file.docker-compose.http.yml:# Edit credentials in docker-compose.http.yml first
docker compose -f docker-compose.http.yml up -d --build
docker logs -f synology-mcp-http
You should see the server log Starting Streamable HTTP MCP server on http://0.0.0.0:8765/mcp and the auto-login succeed. uvicorn's own Uvicorn running on … banner is not printed at the compose file's defaults — it is INFO on the uvicorn.error logger, which the server pins to warning unless DEBUG=true.
Most MCP clients require HTTPS, so the HTTP endpoint must be fronted by a TLS-terminating reverse proxy. For DSM users, the built-in Login Portal → Reverse Proxy does the job:
HTTPS, hostname synology-mcp.example.com, port 443HTTP, localhost, port 8765Connection: upgrade only for real upgrade requests), but it is not what keeps a stream openFor Nginx, the equivalent is:
location / {
proxy_pass http://localhost:8765;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# Responses may stream as long-lived text/event-stream
proxy_buffering off;
proxy_cache off;
proxy_read_timeout 24h;
}
In Claude Desktop (or any MCP client that supports remote connectors), add a custom connector pointing at:
https://synology-mcp.example.com/mcp
The path is whatever MCP_HTTP_PATH is set to (default /mcp). No command, no args, no local Python — just a URL.
The server does not implement any application-level authentication — anything that can reach the HTTP endpoint can call every tool. It does enable the MCP SDK's DNS-rebinding protection, which rejects requests whose Host/Origin headers are not on an allowlist (MCP_HTTP_ALLOWED_HOSTS / MCP_HTTP_ALLOWED_ORIGINS, defaulting to loopback). Behind a reverse proxy set both, minding the differing formats — hosts are bare (synology-mcp.example.com), origins are scheme-qualified (https://synology-mcp.example.com), as in the commented examples in docker-compose.http.yml. That guards browsers against rebinding attacks; it is not authentication. Mitigations:
docker-compose.http.yml binds 127.0.0.1:8765) so only a same-host reverse proxy can reach itNew unified architecture supports both clients simultaneously!
ENABLE_XIAOZHI=true
XIAOZHI_TOKEN=your_xiaozhi_token_here
# Same command, different behavior based on environment
python main.py
# OR
docker-compose up
Claude/Cursor only mode:
🚀 Synology MCP Server
==============================
📌 Claude/Cursor only mode (ENABLE_XIAOZHI=false)
Both clients mode:
🚀 Synology MCP Server with Xiaozhi Bridge
==================================================
🌟 Supports BOTH Xiaozhi and Claude/Cursor simultaneously!
synology_status - Check authentication status and active sessionssynology_list_nas - List all configured NAS units from settings.jsonsynology_login - Authenticate with Synology NAS (conditional)synology_logout - Logout from session (conditional)list_shares - List all available NAS shareslist_directory - List directory contents with metadata
path (required): Directory path starting with /get_file_info - Get detailed file/directory information
path (required): File path starting with /get_file_content - Read strict UTF-8 text or lossless base64 content
path (required): File path starting with /encoding (optional): text (default) or base64max_bytes (optional): Maximum raw bytes to read (default 1 MiB, hard limit 8 MiB)search_files - Recursively search for files and folders by name
path (required): Search directorypattern (required): Case-insensitive substring of the name (e.g., invoice, .pdf). Wildcards are not special — DSM matches report and *report* identically.create_file - Create new files with content
path (required): Full file path starting with /content (optional): File content (default: empty string)overwrite (optional): Overwrite existing files (default: false)encoding (optional): text (default) or strict base64; decoded content is limited to 8 MiBcreate_directory - Create new directories
folder_path (required): Parent directory path starting with /name (required): New directory nameforce_parent (optional): Create parent directories if needed (default: false)delete - Delete files or directories (auto-detects type)
path (required): File/directory path starting with /rename_file - Rename files or directories
path (required): Current file pathnew_name (required): New filenamemove_file - Move files to new location
source_path (required): Source file pathdestination_path (required): Destination pathoverwrite (optional): Overwrite existing filescopy_file - Copy a regular file inside the NAS without sending its bytes through the MCP client
source_path (required): Source file pathdestination_folder (required): Existing destination directory; the filename is preservedoverwrite (optional): Overwrite an existing same-named file (default: false)copy_file verifies the destination path and byte count. It is not a consistent
backup method for a live SQLite database; use SQLite's online backup mechanism
for databases that may be changing during the copy.
ds_get_info - Get Download Station informationds_list_tasks - List all download tasks with status
offset (optional): Pagination offsetlimit (optional): Max tasks to returnds_create_task - Create new download task
uri (required): Download URL or magnet linkdestination (optional): Download folder pathds_pause_tasks - Pause download tasks
task_ids (required): Array of task IDsds_resume_tasks - Resume paused tasks
task_ids (required): Array of task IDsds_delete_tasks - Delete download tasks
task_ids (required): Array of task IDsforce_complete (optional): Force delete completedds_get_statistics - Get download/upload statisticssynology_system_info - Get system model, serial, DSM version, uptime, temperaturesynology_utilization - Get real-time CPU, memory, swap, and disk I/O utilizationsynology_disk_health - List all physical disks with SMART status, model, temp, sizesynology_disk_smart - Get detailed SMART attributes for a specific disksynology_volume_status - List all volumes with status, size, usage, filesystem typesynology_storage_pool - List RAID/storage pools with level, status, member diskssynology_lun_list - List all iSCSI LUNs with name, UUID, size, type, status and backing volume. To see which target a LUN is attached to, use synology_target_list - DSM does not report mappings on the LUN side.synology_lun_get - Get details for a single iSCSI LUN
name (required): LUN name or UUID from synology_lun_list outputsynology_network - Get network interface status and transfer ratesWraps SYNO.Core.ISCSI.LUN and SYNO.Core.ISCSI.Target. Verified against DSM
7.3.2-86009 Update 4 on an RS1221+; other DSM builds may differ, and DSM's own
refusal is reported as given rather than second-guessed.
synology_lun_create - Create a LUN on a volume; returns its uuid and lun_id
name, location (e.g. /volume2), size (in bytes) requiredtype (optional): thin (default, DSM BLUN), advanced, file, or a raw
DSM type name. Note thin and THIN are different: lowercase is the
friendly alias for BLUN, uppercase is DSM's distinct legacy type. Thick
types were refused on the btrfs volume this was tested against.description (optional)synology_lun_delete - DESTRUCTIVE. Delete a LUN and everything on it
uuid and confirm: true requiredsynology_target_list - List targets with IQN, auth type, and the LUNs mapped to eachsynology_target_get - Get one target by target_idsynology_target_create - Create a target; returns its target_id
name required; iqn defaults to iqn.2000-01.com.synology:<name>chap_user + chap_password enable CHAP. Supply both or neither -
one alone, or an empty string, is refused rather than quietly producing a
target with no authentication. With neither, the target accepts any
initiator that can reach it.max_sessions (optional, 0 = DSM default)synology_target_map_lun - Map LUNs to a target (target_id, lun_uuids)synology_target_unmap_lun - DESTRUCTIVE. Unmap LUNs, disconnecting any
initiator using them (target_id, lun_uuids, confirm: true)These tools reject any argument they do not declare, rather than ignoring it: a
misspelled chap_user would otherwise create an unauthenticated target, and a
misspelled type would silently take the default.
synology_ups - Get UPS status, battery level, power readingssynology_services - List installed packages and their running statussynology_system_log - Get recent system log entriessynology_health_summary - Aggregate system info, utilization, disk health, and volume statussynology_container_list - List Container Manager containers
offset (optional): Pagination offsetlimit (optional): Maximum containers to returncontainer_type (optional): Container filter (default: all)synology_container_health_summary - Summarize container status, health, restart counts, and imagessynology_container_disk_usage - Show the read-only disk-usage summary available through Container Manager APIssynology_container_get - Get a Container Manager container
name (required): Container namesynology_container_start - Start a Container Manager container
name (required): Container namesynology_container_stop - Stop a Container Manager container
name (required): Container namesynology_container_restart - Restart a Container Manager container
name (required): Container namesynology_container_delete - Delete a Container Manager container
name (required): Container nameforce (optional): Force deletion (default: false)preserve_profile (optional): Preserve Synology container profile (default: true)synology_container_logs - Get Container Manager container logs
name (required): Container namesince (optional): Log start time/filteroffset (optional): Pagination offset (default: 0)limit (optional): Maximum log lines to return (default: 1000)synology_container_resource - Get real-time resource usage for a Container Manager container
name (required): Container namesynology_container_project_list - List Container Manager projectssynology_container_project_get - Get a Container Manager project (Compose, environment, and secret fields are omitted)
name (required): Project namesynology_container_project_create - Create and save a Container Manager project definition
name (required): Project nameshare_path (required): Project folder path on the NAScontent (required): Docker Compose YAML contentenable_service_portal (optional): Enable Synology service portal (default: false)service_portal_name (optional): Service portal nameservice_portal_port (optional): Service portal portservice_portal_protocol (optional): Service portal protocol (default: http)synology_container_project_build to materialize it.synology_container_project_update - Update a Container Manager project
name (required): Project namecontent (required): Docker Compose YAML contentenable_service_portal (optional): Enable Synology service portalservice_portal_name (optional): Service portal nameservice_portal_port (optional): Service portal portservice_portal_protocol (optional): Service portal protocolsynology_container_project_start - Start a Container Manager project
name (required): Project namesynology_container_project_stop - Stop a Container Manager project
name (required): Project namesynology_container_project_restart - Restart a Container Manager project
name (required): Project namesynology_container_project_build - Materialize or rebuild a saved Container Manager project
name (required): Project namesynology_container_project_clean - Clean a Container Manager project
name (required): Project namesynology_container_project_delete - Delete a Container Manager project
name (required): Project namesynology_container_image_list - List Container Manager images
offset (optional): Pagination offsetlimit (optional): Maximum images to returnshow_dsm (optional): Include DSM images (default: false)synology_container_image_get - Get a Container Manager image
name (required): Image repository nametag (optional): Image tag (default: latest)synology_container_image_delete - Delete a Container Manager image
name (required): Image repository nametag (optional): Image tag (default: latest)synology_container_image_prune - Remove images unused by any container
synology_container_image_prune_preview provides a read-only candidate list before cleanupsynology_container_image_pull - Pull a Container Manager image
repository (required): Image repository nametag (optional): Image tag (default: latest)synology_container_registry_list - List Container Manager registriessynology_container_registry_search - Search Container Manager registries
query (required): Image search queryoffset (optional): Pagination offsetlimit (optional): Maximum results to returnsynology_container_registry_tags - List tags for a registry image
repository (required): Image repository nameoffset (optional): Pagination offsetlimit (optional): Maximum tags to returnsynology_container_registry_download - Download a registry image
repository (required): Image repository nametag (optional): Image tag (default: latest)synology_container_network_list - List Container Manager networkssynology_container_network_get - Get a Container Manager network
name (required): Network namesynology_container_network_create - Create a Container Manager network
name (required): Network namedriver (optional): Network driver (default: bridge)subnet (optional): Subnet CIDRgateway (optional): Gateway IPip_range (optional): Allocatable IP range CIDRenable_ipv6 (optional): Enable IPv6 (default: false)synology_container_network_delete - Delete a Container Manager network
name (required): Network namesynology_nfs_status - Get NFS service status and configurationsynology_nfs_enable - Enable or disable the NFS servicesynology_nfs_list_shares - List all shared folders with their NFS permissionssynology_nfs_set_permission - Set NFS client access permissions on a shared foldersynology_reverse_proxy_list - List reverse proxy entries (Control Panel → Login Portal → Advanced → Reverse Proxy) with source, destination, HSTS, WebSocket, custom headers and access control profilesynology_reverse_proxy_get - Get one entry by UUID or descriptionsynology_access_control_profile_list - List the access control profiles an entry can referencesynology_reverse_proxy_create - Create an entry; refused if the description is already in usesynology_reverse_proxy_update - Change some fields of an entry, keeping the restsynology_reverse_proxy_delete - DESTRUCTIVE. Delete an entry (requires confirm=true)outcome_unknown: true — list before retrying.For Claude Code, Claude Desktop, and claude.ai users, this repo ships an Anthropic Agent Skill that teaches Claude how to use the MCP tools effectively — picking the right tool, targeting the right NAS in multi-NAS setups, preferring aggregate health checks over fan-out calls, and using correct path conventions.
The skill lives at skills/synology-nas/ and uses progressive disclosure across seven domains (auth, files, downloads, health, containers, shares/NFS, user management).
Install:
~/.claude/skills/synology-nas/synology-nas/ folder via the Skills settings pageThe skill is purely additive — it works alongside the MCP and only triggers on Synology/NAS-related prompts.
⚠️ Security Warning: Use a Dedicated Account
For this MCP server, create a dedicated Synology user account with appropriate permissions. This account should:
- Have minimal required permissions only (not admin!)
- Be used exclusively for MCP server automation
- 2FA is now supported — if your DSM account has 2FA enabled, see the 2FA / OTP Accounts section below to supply an
otp_code(one-shot) ordevice_id(persistent) field. Older guidance of "no 2FA" is no longer required.
*Required for auto-login and default operations
For managing multiple Synology NAS devices, use the XDG standard config directory (~/.config/synology-mcp/settings.json):
mkdir -p ~/.config/synology-mcp
touch ~/.config/synology-mcp/settings.json
chmod 600 ~/.config/synology-mcp/settings.json # Important: secure permissions!
Note: This follows the XDG Base Directory Specification - ~/.config/ is the standard location for user configuration files on Linux/macOS. You can customize the location by setting the XDG_CONFIG_HOME environment variable.
With Docker:
The docker-compose.yml automatically mounts your ~/.config/synology-mcp directory into the container at /home/mcpuser/.config/synology-mcp, so multi-NAS works out of the box with Docker as well.
settings.json format:
{
"synology": {
"nas1": {
"host": "192.168.1.100",
"port": 5000,
"username": "admin",
"password": "your_password",
"note": "Primary NAS at home"
},
"nas2": {
"host": "192.168.1.200",
"port": 5001,
"username": "admin",
"password": "your_password",
"note": "Backup NAS"
},
"nas3": {
"url": "https://nas.example.com",
"username": "admin",
"password": "your_password",
"note": "NAS behind a reverse proxy"
}
},
"xiaozhi": {
"enabled": false,
"token": "your_xiaozhi_token",
"endpoint": "wss://api.xiaozhi.me/mcp/"
},
"server": {
"auto_login": true,
"verify_ssl": false,
"session_timeout": 3600,
"debug": false,
"log_level": "INFO"
}
}
Configuration fields:
*Either host or url is required per NAS entry.
Notes:
host/port form always appends a port and derives the scheme from it, so it cannot express https://nas.example.com on the default 443 — set url directly for reverse-proxied setupschmod 600 ~/.config/synology-mcp/settings.json is required for securitysettings.json File Permissions:
chmod 600 ~/.config/synology-mcp/settings.json is required. The server refuses to load the file if it is group- or world-readable/writable, or owned by another user.NT AUTHORITY\SYSTEM, and BUILTIN\Administrators. Any inherited Everyone / BUILTIN\Users / Authenticated Users grant fails the check.
Requires the optional pywin32 package: pip install pywin32. If pywin32 is not installed, the server fails closed and refuses to load settings.json. Operators who accept the risk of an unverified file can opt back in by setting SYNOLOGY_MCP_ALLOW_UNVERIFIED_WINDOWS_ACL=true.
The server resolves the file via XDG_CONFIG_HOME (default Path.home() / ".config"), so on Windows it lives at %USERPROFILE%\.config\synology-mcp\settings.json unless XDG_CONFIG_HOME is set.
Lock down the file from an elevated PowerShell prompt (uses the same path the server loads):
# Resolve the path the SAME way the server does: $XDG_CONFIG_HOME if set,
# otherwise %USERPROFILE%\.config. This honors the override documented above.
$cfg = if ($env:XDG_CONFIG_HOME) { $env:XDG_CONFIG_HOME } else { "$env:USERPROFILE\.config" }
$f = "$cfg\synology-mcp\settings.json"
# The server's ACL audit requires: owner == current user, no NULL DACL, and
# no allow-ACE outside {current user, SYSTEM, Administrators}. The steps
# below enforce all three.
#
# Use the *<SID> form for every built-in principal: account names like
# "Administrators" / "Everyone" / "Users" are localized on non-English
# Windows (e.g. German "Administratoren") and won't resolve. The
# locale-independent SIDs:
# *S-1-1-0 Everyone
# *S-1-5-11 Authenticated Users
# *S-1-5-32-545 BUILTIN\Users
# *S-1-5-32-544 BUILTIN\Administrators
#
# 1. Ensure the file is owned by the current user (the audit rejects any
# other owner). /setowner requires elevation.
icacls $f /setowner "${env:USERNAME}"
# 2. Drop inherited ACEs, then revoke the common foreign grants. /grant:r
# only replaces the named principal, so revoke first.
icacls $f /inheritance:r
icacls $f /remove:g "*S-1-1-0" "*S-1-5-11" "*S-1-5-32-545"
# Re-run `icacls $f` here; if any principal other than your user or
# Administrators still appears, run: icacls $f /remove:g "<that principal>"
# 3. Grant the current user and Administrators full control.
icacls $f /grant:r "${env:USERNAME}:(F)"
icacls $f /grant:r "*S-1-5-32-544:(F)" # BUILTIN\Administrators (locale-independent)
If the file is brand new, the /remove:g step is a harmless no-op.
Verify: icacls "$f" — only your user and *S-1-5-32-544 (Administrators) should appear.
SSL Certificate Verification (VERIFY_SSL):
false to support self-signed certificates on internal NAS devicesVERIFY_SSL=trueVERIFY_SSL=false disables certificate verification and makes your connection vulnerable to man-in-the-middle (MITM) attacksAuto-Login (AUTO_LOGIN):
true for convenience with settings.json~/.config/synology-mcp/settings.json with 0600 permissionsAUTO_LOGIN=false and use the synology_login tool2FA / OTP Accounts (optional):
The MCP server supports DSM accounts with 2FA enabled. There are two ways to use it:
One-shot OTP via synology_login tool (interactive):
{ "base_url": "https://nas.lan:5001", "username": "alice", "password": "…", "otp_code": "123456" }
DSM will return a did (device token) in the response — copy that value into settings.json (below) to skip OTP on future process restarts.
Persistent trusted-device token (recommended for AUTO_LOGIN=true):
Add otp_code (one-shot, first login only) and/or device_id (long-lived, ongoing) fields per-NAS in settings.json:
{
"synology": {
"nas1": {
"host": "192.168.1.100", "port": 5001,
"username": "alice", "password": "…",
"otp_code": "123456",
"note": "primary — 2FA enabled"
}
}
}
Workflow:
otp_code to a fresh 6-digit code from your authenticator and start the server.nas1: 2FA bootstrap — copy this device_id into settings.json to skip OTP on future starts: <did>
Copy the <did> value.device_id and delete otp_code.When device_id is present, it takes precedence over otp_code (trusted-device path). Legacy .env users can set the one-shot SYNOLOGY_OTP_CODE env var; for persistent device_id, migrate to settings.json (long opaque token doesn't fit an env var cleanly).

// List directory
{
"path": "/volume1/homes"
}
// Search for PDFs
{
"path": "/volume1/documents",
"pattern": ".pdf"
}
// Create new file
{
"path": "/volume1/documents/notes.txt",
"content": "My important notes\nLine 2 of notes",
"overwrite": false
}

// Delete file or directory (auto-detects type)
{
"path": "/volume1/temp/old-file.txt"
}
// Move file
{
"source_path": "/volume1/temp/file.txt",
"destination_path": "/volume1/archive/file.txt"
}

// Create download task
{
"uri": "https://example.com/file.zip",
"destination": "/volume1/downloads"
}
// Pause tasks
{
"task_ids": ["dbid_123", "dbid_456"]
}

main.py supports both stdio and WebSocket clientsENABLE_XIAOZHI environment variablemcp-server-synology/
├── main.py # 🎯 Unified entry point
├── src/
│ ├── mcp_server.py # Standard MCP server
│ ├── multiclient_bridge.py # Multi-client bridge
│ ├── auth/ # Authentication modules
│ ├── filestation/ # File operations
│ └── downloadstation/ # Download management
├── docker-compose.yml # Single service, environment-controlled
├── Dockerfile
├── pyproject.toml # Dependencies (single source of truth)
└── .env # Configuration
ENABLE_XIAOZHI=false → main.py → mcp_server.py (stdio only)ENABLE_XIAOZHI=true → main.py → multiclient_bridge.py → mcp_server.py (both clients)Perfect for any workflow - from simple Claude/Cursor usage to advanced multi-client setups! 🚀
💾 Model Context Protocol (MCP) server for Synology NAS - Enables AI assistants (Claude, Cursor, Continue) to manage files, downloads, and system operations through secure API integration. Features Do
ओवरव्यू
💾 Model Context Protocol (MCP) server for Synology NAS - Enables AI assistants (Claude, Cursor, Continue) to manage files, downloads, and system operations through secure API integration. Features Docker deployment, auto-authentication, and comprehensive file system tools.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
MCP Server Synology stdio पर लोकल चलता है।
पिछली जाँच 2026-10-26 को हुई। 💾 Model Context Protocol (MCP) server for Synology NAS - Enables AI assistants (Claude, Cursor, Continue) to manage files, downloads, and system operations through secure API integration. Features Docker deployment, auto-authentication, and comprehensive file system tools.