synology-mcp
Related Servers
Alternatives to synology-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude to inspect and troubleshoot a Synology NAS, including system health, storage, Docker containers and logs, Watchtower updates, backups, security scans, and permitted files, in a read-only configuration.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude or any other MCP client to manage a Synology NAS running DSM 7 — system health, disks and storage, files, Container Manager, packages, accounts and shares, security, Photos, Drive, Synology Office and any other DSM API. It handles 2FA through a stored trusted-device token, pins the NAS's certificate before sending credentials, gates tools behind read/write/admin permission tiers, and previews risky changes like deletions or public sharing.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage Synology NAS devices with file operations (create, delete, move, search) and Download Station control through secure authentication and session management.144 PyPI254MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to query a Synology NAS through MCP for system health, storage, network, packages, power, Cloud Sync, scheduled tasks, logs, notifications, and files, with read-only access by default and optional write permission for Cloud Sync controls.16MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage files on Synology NAS via the File Station API, supporting operations like browsing, searching, uploading/downloading, creating, renaming, copying, moving, deleting, compressing, and extracting.MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude to your self-hosted or cloud-based Seafile storage for managing libraries and files through natural language. It enables users to browse directories, read file contents, and perform file operations like moving, renaming, or searching across their private infrastructure.4MIT
TDQS
Scored across 33 tools
Tools are partitioned by subsystem (File Station, system/storage, Synology Drive, Download Station) with distinct descriptions, so overlaps like list_files vs drive_list vs list_shares are resolvable. Minor confusion remains: bare 'get_info' (File Station user info) sits next to 'get_system_info', and drive_list_labels vs drive_list_labelled are near-homonyms. Overall mostly distinct with a couple of easily-mistaken pairs.
Consistent snake_case verb_noun pattern dominates: list_files, get_file_info, search_files, get_disk_health, drive_search, downloads_list. Deviations are minor: differing prefix conventions (drive_ singular vs downloads_ plural), noun-number inconsistency (list_files vs get_info/get_md5), and the vague bare 'get_info'.
33 tools is heavy for a single server, though it legitimately spans four distinct subsystems (files, system health, Drive, Download Station). Each tool does earn a place individually, but the surface is large enough that an agent must scan many similar-sounding entries. Borderline over-scoped rather than bloated with filler.
Read/query coverage is thorough, but the surface is essentially read-only: no upload, create folder, copy/move/delete/rename, or share-link creation, even though background tasks for those operations are listed. Download Station is likewise read-only (info/list/get but no add, pause, or remove task). Agents asked to modify anything will hit a dead end.