sonarr-mcp
Related Servers
Alternatives to sonarr-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI assistants to manage TV series collections through Sonarr's API using natural language interactions. Supports searching, adding, updating, and deleting TV series with detailed control over quality profiles, season monitoring, and episode downloads.9-
- AlicenseCqualityAmaintenanceEnables full control of Sonarr from Claude.ai and Claude Code by exposing all 234 v3 API operations as tools for managing media libraries.2349 npmMIT
- AlicenseBqualityAmaintenanceExposes the Sonarr v3 REST API as MCP tools, enabling LLMs to read and manage a Sonarr instance including series, episodes, downloads, history, and more. Supports both read and write operations, with destructive tools flagged.15MIT
- AlicenseBqualityCmaintenanceEnables managing a Sonarr TV show instance through natural language, including series and episode management, download queue monitoring, calendar tracking, and configuration of quality profiles and root folders.24MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage TV shows and movies via Sonarr and Radarr, including searching, adding, and monitoring downloads.-
- 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
TDQS
Scored across 136 tools
Each tool targets a distinct Sonarr resource or action, and list/get pairs are explicitly distinguished (e.g. list_series compact vs get_series full). A small number of near-duplicates (run_command vs the dedicated search/refresh tools, get_queue vs get_queue_details, singular/plural delete and remove variants) require careful reading but are not genuinely interchangeable.
The vast majority follow a consistent verb_noun snake_case pattern with list/get/create/update/delete/test prefixes. Minor deviations exist: edit_series_bulk uses edit instead of update, plural/singular variants are mixed (delete_episode_file vs delete_episode_files), and list_tag_details/run_command don't quite fit the resource pattern.
136 tools is an extreme count for an MCP server, even for a full application API. The calibration considers 50+ an extreme mismatch, and this many tools creates significant selection overhead and makes it hard for an agent to identify the right operation.
The surface is exceptionally broad, covering library management, episode monitoring, searching, queue/history/blocklist, quality profiles, custom formats, indexers, download clients, import lists, notifications, tags, configurations, logs, backups, and system operations. Minor gaps remain—delay profiles only have list (no create/update/delete) and host config has get but no update.