sonarr-mcp
Related Servers
Alternatives to sonarr-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityBmaintenanceConnects AI agents to Sonarr, exposing 136 tools for managing a TV library — adding series, chasing missing episodes, fixing the download queue, tuning quality profiles, and diagnosing health issues.1368 npmMIT
- AlicenseBqualityAmaintenanceMCP server exposing Seerr's full v1 REST API as tools, enabling LLMs to search and discover media, manage requests and approvals, users, issues, watchlists, and integration settings for Plex/Jellyfin/Emby and Sonarr/Radarr, including reads and writes with destructive operations flagged.15MIT
- AlicenseBqualityAmaintenanceMCP server that exposes the Bookshelf (Readarr fork) v1 REST API as tools, allowing an LLM to read and manage authors, books, book files, editions, series, download queue, history, indexers, import lists, custom formats, tags, commands, and system status, with full read/write access and 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
- 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-
TDQS
Scored across 15 tools
Multiple generic dispatcher tools (like sonarr_profiles_formats, sonarr_config) overlap with the many specific CRUD tools, causing ambiguous selection. Additionally, singular/plural inconsistencies such as sonarr_update_qualitydefinition vs sonarr_update_quality_definitions blur the boundaries further.
The convention is mostly sonarr_<resource>_<action> but verbs vary widely (list, get, create, update, delete, bulk_update, mark, grab, reorder, push, search, commit, restart, shutdown, ping) and resource names mix singular and plural forms (e.g., qualitydefinition vs quality_definitions). Generic tools like sonarr_config lack any verb entirely.
The server lists well over 100 individual tools, far exceeding the typical 3-15 tool sweet spot and even the 50+ threshold for an extreme mismatch. This enormous surface makes it impractical for an agent to navigate effectively.
The tool set is remarkably comprehensive, covering essentially every Sonarr API endpoint: series, episodes, files, quality profiles, indexers, download clients, import lists, notifications, metadata, queue, history, blocklist, tags, calendar, and system commands. It supports full CRUD and additional operations for most resources, leaving no obvious dead ends.