MCP *arr Server
Related Servers
Alternatives to MCP *arr Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sonarr and Radarr APIs to query media libraries, check recent additions, view upcoming releases, manage download queues, and perform searches for TV shows and movies through natural language.1MIT
- FlicenseAqualityDmaintenanceEnables users to manage Sonarr and Radarr instances through natural language, allowing search, addition, deletion, and monitoring of TV series and movies.60-
- FlicenseNot gradedqualityDmaintenanceIntegrates with Radarr and Sonarr to manage your media library, enabling search, download requests, status checks, and system health monitoring.6-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage TV shows and movies via Sonarr and Radarr, including searching, adding, and monitoring downloads.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage media automation services like Sonarr, Radarr, Prowlarr, Bazarr, Overseerr, and Plex through natural language commands.9MIT
- AlicenseAqualityDmaintenanceEnables 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.7027 npm1MIT
TDQS
Scored across 73 tools
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.
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.
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.
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.