Skip to main content
Glama

Related Servers

Alternatives to MCP *arr Server

No user-submitted related servers found.

    Related Servers

    TDQS

    B3.3/5.0

    Scored across 73 tools

    Disambiguation4/5

    Service prefixes and action-specific names make most tools clearly distinct. However, several search-related tools overlap in wording (search, arr_search_all, prowlarr_search, sonarr_search, radarr_search vs radarr_search_movie, lidarr_search vs lidarr_search_album), so agents may need descriptions to avoid misselection.

    Naming Consistency4/5

    Most tools follow a predictable service_verb_noun pattern such as sonarr_get_series, radarr_add_movie, and lidarr_search_album. The main deviations are the generic search/fetch tools and arr_status/arr_search_all, which break the service-prefix convention but remain understandable.

    Tool Count2/5

    Seventy-three tools is far above the typical 3-15 sweet spot and creates a heavy navigation burden for an agent. The breadth across four *arr services plus TRaSH explains some of the count, but the repeated per-service config getters make the surface unnecessarily large.

    Completeness3/5

    Core discovery, add, search, queue, and configuration-read workflows are covered for Sonarr, Radarr, Lidarr, and Prowlarr. However, Sonarr and Lidarr lack update/delete operations for series/artists and queue-item removal, Prowlarr lacks indexer CRUD, and Sonarr lacks the manual-import/command-status workflow that Radarr has.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling