arr-mcp
Related Servers
Alternatives to arr-mcp
- AlicenseNot gradedqualityBmaintenanceA locally-run, read-only MCP server that lets an LLM client diagnose a self-hosted *arr media stack by aggregating across Sonarr, Radarr, Prowlarr, qBittorrent, Tdarr, and Profilarr.76 PyPIApache 2.0
- AlicenseAqualityCmaintenanceMCP server to manage your *ARR media stack (Radarr, Sonarr, Lidarr, Readarr, Prowlarr) for searching, adding, and managing movies, TV shows, music, books, and indexers.1ISC
- AlicenseNot gradedqualityCmaintenanceUnified MCP server for media acquisition, subtitle automation, and agent-run media workflows, enabling downloads via Prowlarr/qBittorrent and subtitle translation/sidecar creation.1MIT
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that exposes Sonarr, Radarr, Lidarr, and Jellyfin to any MCP client through a curated tool layer for LLM consumption.38 PyPIMIT
- AlicenseAqualityCmaintenanceMCP server for managing a media server stack (Plex, Radarr, Overseerr, Bazarr, Prowlarr, Trakt.tv) using natural language to browse, request, and discover content.12MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI assistants control over your Sonarr, Radarr, Prowlarr, qBittorrent, and Jellyfin homelab media stack.8MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server for safely searching, reading, summarizing, tagging, deduplicating, and organizing local files with scoped access, read-only defaults, and dry-run plans.19MIT
- AlicenseAqualityBmaintenanceAn MCP server for the Servarr stack — Sonarr, Radarr, Lidarr, Readarr, and Prowlarr — packaged as a Docker container. Lets an MCP client (Claude Desktop, etc.) browse and search whichever \*arr apps you're running.291MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that enables interaction with Sonarr, Radarr, and Prowlarr through their APIs, allowing management and queries via MCP over stdio.15 npm1MIT
TDQS
Scored across 44 tools
Most tools have clearly distinct resource/action targets, and the descriptions explicitly separate close pairs such as get_queue vs get_history, add_media vs request_media, and search_media vs discover_media. With 44 tools there are still overlapping search/media/metadata areas, but the boundaries are documented well enough that misselection should be uncommon.
Names are consistently snake_case and generally verb-first (get_*, delete_*, update_*, trigger_*, fix_*). Minor deviations like respond_to_request and blocklist_media keep it from being perfectly uniform, but the convention is predictable.
44 tools is far above the typical well-scoped range for a single MCP server. The broad multi-service stack partially justifies the surface, but it is still heavy enough to increase selection cost and coordination burden.
The set covers a wide media-automation lifecycle: library/search, add/update/delete, monitoring, queue/history, downloads, indexers, requests, subtitles, metadata, health, and profile issues. Some peripheral operations are missing, such as full quality-profile management or richer Seerr issue handling, but core workflows have no major dead ends.