nas-search-mcp
Related Servers
Alternatives to nas-search-mcp
No user-submitted related servers found.
Related Servers
- 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 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
- AlicenseAqualityBmaintenanceEnables self-hosted access to Synology NAS files, system monitoring, container management, and download tasks through MCP clients, with optional connectivity to ChatGPT via a secure tunnel.31MIT
- FlicenseAqualityDmaintenanceMCP server enabling AI agents to manage and monitor Synology NAS via official DSM API, including file operations, system stats, backups, downloads, and camera lists.15-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect and operate a UGOS Pro NAS through its built-in HTTPS API via 25 tools covering system stats, storage volumes, files, downloads, photos, and media libraries, without SSH. Read-only tools run directly, write tools prompt for confirmation, destructive deletes require an explicit second confirmation, and it can be deployed either locally over stdio or on the NAS via Docker SSE.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query QNAP QTS NAS status, health, storage, network, and Tailscale diagnostics through five read-only stdio tools, with no general shell or arbitrary API access.2MIT
TDQS
Scored across 2 tools
The two tools serve entirely different purposes: 'search' performs content/name queries over the NAS, while 'status' only reports session metadata (expiry, folders, counters, last error). There is no realistic scenario where an agent would confuse the two, and the descriptions reinforce the distinction.
Both names are single, lowercase, underscore-free tokens with no prefix clutter, so the style is consistent. The only minor deviation is grammatical: 'search' is a verb while 'status' is a noun, which slightly breaks a verb_noun prediction but remains perfectly readable.
Two tools is thin even for a search-only server; the surface is essentially one operation plus a diagnostics call. The narrow purpose prevents it being a mismatch, but there is little headroom for anything beyond querying and checking state.
Search covers paging (offset/next_offset), sizing, and a detailed error taxonomy, which is solid for the core workflow. However, there is no way to browse a share or folder hierarchy, inspect a single file's details, or start/refresh the search session — a missing-session error (exit_code 8) leaves the agent with only 'ask the user', a dead end.