Skip to main content
Glama

Related Servers

Alternatives to arr-doctor

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to monitor and manage a self-hosted media stack—including Sonarr, Radarr, Prowlarr, Bazarr, Overseerr, qBittorrent, and Jellyfin—through tools for status, queues, searches, additions, requests, downloads, and now-playing checks. It also supports arbitrary API calls with safety levels and secret redaction.
      10
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Desktop to troubleshoot and manage a self-hosted Plex + Servarr media stack, including diagnosing missing media, monitoring download queues and indexer health, and coordinating operational tasks across Radarr, Sonarr, SABnzbd, qBittorrent, Tautulli, TMDb, Prowlarr, and remote hosts.
      17
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with the *arr media management suite (Sonarr, Radarr, Lidarr, Prowlarr, SABnzbd) and TRaSH Guides through MCP tools, allowing media library management, searching, and configuration via natural language.
      70
      6 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables control of a home lab through a single MCP server, exposing tools for Home Assistant, Portainer, Sonarr, Radarr, SABnzbd, and Jellyfin so Claude can query states, manage containers and stacks, handle media libraries and download queues, and run automations. Each service is optional and can be configured via environment variables, with a read-only mode and bearer-token-protected HTTP transport for always-on deployments.
      1
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Enables full control of Sonarr from Claude.ai and Claude Code by exposing all 234 v3 API operations as tools for managing media libraries.
      235
      30 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes and detailed descriptions help differentiate (e.g., parse_release vs explain_search vs grab_release). However, several diagnostic tools overlap: find_stalled_downloads vs get_queue's stall detection, check_paths vs get_health, and library_report vs get_disk_space, creating some risk of misselection.

    Naming Consistency4/5

    Almost all tools use snake_case with consistent verb_noun patterns (get_queue, search_episodes, add_series). Minor deviations like library_report (noun_report) and manual_import (adjective_noun) are readable but slightly break the convention.

    Tool Count2/5

    36 tools far exceeds the typical 3-15 well-scoped range and surpasses the 25+ threshold for 'too many'. While the domain is broad, many tools could be consolidated or scoped down without losing core functionality.

    Completeness3/5

    The surface is extensive for diagnostics and many management tasks (queue, history, health, imports, renaming, bulk edits). But notable gaps exist: no add_movie tool despite Radarr support, and no way to delete a series/movie from the library, which can block common lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues