Skip to main content
Glama
arr-mcps

dashbrr-mcp

Official
by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to dashbrr-mcp

No user-submitted related servers found.

    Related Servers

    • dashy-mcp

      SavageCore
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Dashy's REST API as tools, enabling an LLM to read and edit dashboard config, including sections, items, and top-level config keys.
      4
      MIT
    • profilarr-mcp by arr-mcps

      profilarr-mcpofficial

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Profilarr's v1 REST API as tools, enabling an LLM to inspect and manage linked databases, connected Radarr/Sonarr instances, backups, jobs, announcements, and system status.
      20
      MIT

    • autobrr-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing autobrr's full API as tools, enabling LLMs to read and manage filters, indexers, feeds, clients, actions, releases, and system config. It wraps approximately 104 endpoints into 13 resource-scoped tools for comprehensive autobrr instance management.
      13
      MIT

    • seerr-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      MCP server exposing Seerr's full v1 REST API as tools, enabling LLMs to search and discover media, manage requests and approvals, users, issues, watchlists, and integration settings for Plex/Jellyfin/Emby and Sonarr/Radarr, including reads and writes with destructive operations flagged.
      15
      MIT

    • qbit_manage-mcp

      arr-mcps
      A
      license
      A
      quality
      B
      maintenance
      MCP server exposing qbit_manage's Web API as tools, so an LLM can read and manage a qbit_manage instance: run maintenance commands on qBittorrent torrents, manage config files, scheduler, logs, security settings, and system state.
      6
      MIT
    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

    A3.9/5.0

    Scored across 34 tools

    Disambiguation5/5

    Every tool targets a distinct service or resource, e.g., get_sonarr_queue vs get_sonarr_stats, and health check tools are clearly separated by target (dashbrr itself vs configured services). No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent dashbrr_<verb>_<noun> pattern, with verbs like get, list, create, delete, set, save, check. The minor plural inconsistency in ui_preferences vs ui_preference doesn't affect predictability.

    Tool Count3/5

    At 34 tools, the count is heavy, but the server aggregates many distinct services (autobrr, Jellyfin, Traefik, etc.), so the breadth is justified. Still, the number edges into the 'too many' range for a typical MCP server.

    Completeness4/5

    The surface covers settings CRUD, per-service monitoring summaries, queue deletion for media managers, Overseerr approvals, and Plex auth flow. Missing are some deeper management actions (e.g., trigger scans), but the core dashboard operations are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources