Skip to main content
Glama

Related Servers

Alternatives to dashy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with self-hosted Miniflux instances through the HTTP API, covering feeds, categories, entries, enclosures, icons, OPML, users, and API keys. Write operations are confirm-gated with dry-run previews and secret redaction.
      6 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables managing a self-hosted media library through its HTTP API, with scoped toolsets, confirm-gated writes, dry-run previews, and read caching. Supports libraries, items, collections, playlists, podcasts, sessions, stats, tags, genres, and administrative operations.
      13
      131 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables querying and managing an Unraid server through its official GraphQL API, exposing system, array, Docker, VM, share, notification, metrics, logs, and health actions via a single MCP tool. Write operations are gated by two independent locks and confirmation, with read-only behavior by default.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connects MCP clients to a self-hosted Syncthing instance's GUI REST API for reading configuration, folders, devices, and connections, plus gated write actions like adding or patching folders and devices, scanning, pausing, restarting, and shutting down. Supports stdio and localhost-only Streamable HTTP with API-key auth, dry-run write previews, redaction of secrets, caching, and rate limiting.
      5
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Provides a structured data interface for Servarr apps (Sonarr, Radarr, Prowlarr) enabling health checks, analytics, simulations, backups, and guarded write operations.
      100
      8 npm
      MIT

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are partitioned by resource level (system, whole config file, top-level key, section, item), which is mostly clear. There is some inevitable overlap — dashy_config replace vs dashy_keys replace vs dashy_sections update can all mutate the same document, and dashy_keys get(key=sections) duplicates dashy_sections get — but the descriptions explicitly delineate scope.

    Naming Consistency5/5

    Every tool follows the same dashy_<resource> snake_case noun pattern, and the resource hierarchy (system → config → keys → sections → items) is coherent. Actions are consistently multiplexed via an action parameter rather than encoded in names, so the convention is applied uniformly.

    Tool Count5/5

    Five tools is well-scoped for a dashboard config server, and each one covers a distinct layer of the document rather than being a thin wrapper. The action-multiplexing keeps the surface small (~16 operations) while staying navigable.

    Completeness4/5

    Full lifecycle coverage exists for the hierarchical parts of the config (sections and items have add/update/delete), plus file-level and key-level read/write. Minor gaps: no way to create or delete a config file, and dashy_keys cannot add or remove top-level keys — though those keys are a fixed set, so agents can work around it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues