Skip to main content
Glama
danjam

mcp-synology

by danjam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-synology

No user-submitted related servers found.

    Related Servers

    • Synology NAS MCP

      miku2339
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      1
      MIT

    • Synology_MCP

      DerHary
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Synology NAS services including DSM, File Station, Calendar, Note Station, Contacts, Chat, Download Station, and Container Manager through a modular MCP interface with configurable safety modes.
      MIT

    • mcp-syncnology

      humyai99
      F
      license
      A
      quality
      B
      maintenance
      MCP 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
      -

    • Zabbix MCP Server

      valv111
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query Zabbix monitoring data through MCP, including host briefs and problem reports, with read-only access and whitelist controls.
      -

    • dsm-mcp

      dogeared
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to inspect Synology NAS system, storage, and utilization, and manage Docker containers via the Synology Web API with automatic session handling.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    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).

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources