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
- FlicenseAqualityBmaintenanceEnables 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 gradedqualityCmaintenanceEnables AI assistants to manage TV shows and movies via Sonarr and Radarr, including searching, adding, and monitoring downloads.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage media automation services like Sonarr, Radarr, Prowlarr, Bazarr, Overseerr, and Plex through natural language commands.7MIT
- AlicenseAqualityCmaintenanceEnables 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.7017 npm1MIT
TDQS
Scored across 64 tools
Most tools are clearly scoped by app prefix and resource, but the search family is confusing: generic 'search', 'arr_search_all', 'prowlarr_search', and per-app searches overlap in purpose and only descriptions hint at their differences. The opaque 'fetch' tool also adds ambiguity by not clearly mapping to a destination resource.
The bulk of tools follow a consistent `<app>_<verb>_<noun>` convention, e.g. sonarr_get_quality_profiles, radarr_add_movie, lidarr_search_missing. A few generic tools like 'search', 'fetch', 'arr_status', and 'arr_search_all' break the pattern, but they are few and the overall style remains readable and predictable.
At 64 tools, the surface is extreme and will be unwieldy for an agent to reason about. While the count partially reflects four distinct *arr services, many operations are duplicated per app and the set would benefit from consolidation or a narrower scope.
The server covers configuration review, search, and adding media well across Sonarr, Radarr, Lidarr, and Prowlarr. However, lifecycle coverage is incomplete: Sonarr and Lidarr lack update/delete operations, Radarr lacks movie deletion, Sonarr lacks queue-item removal, and Prowlarr has no indexer add/edit/delete tools.