Sonarr MCP server
Related Servers
Alternatives to Sonarr MCP server
No user-submitted related servers found.
Related Servers
- 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.13684 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
- AlicenseBqualityAmaintenanceEnables running Overseerr or Jellyseerr from Claude.ai and Claude Code, with all 170 API operations exposed as tools for managing requests, settings, users, issues, and media services.170MIT
- 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-
- AlicenseCqualityAmaintenanceExposes all 209 Audiobookshelf API routes as tools, letting Claude.ai and Claude Code manage libraries, books, podcasts, playback, users, settings, and more.20958 npmMIT
- AlicenseCqualityBmaintenanceEnables running Plex from Claude.ai and Claude Code by exposing all 405 operations as tools, covering both your media server and plex.tv cloud services with automatic routing to the appropriate host.40512 npmMIT
TDQS
Scored across 234 tools
Tools are largely grouped by resource (e.g., list_series, get_series_by_id, update_series_by_id) with clear distinctions. However, there are least ten tools that are effectively static resource fetchers or redundant, such as list_root, get_by_path, and list_system_routes_duplicate, which overlap with generic static resource serving. Additionally, update_episodefile_bulk and update_episodefile_editor have similar purposes (bulk updating episode files) and could be confused, requiring careful reading of descriptions.
The naming follows a consistent verb_noun_pattern (e.g., list_series, create_series, delete_series_by_id, update_series_by_id) with occasional suffix variations like _bulk, _editor, _testall, and _schema. However, the naming is inconsistent in the static resource tools—get_by_path, get_content_by_path, list_root, list_login, list_logout—which don't follow the same resource-action pattern as the API tools. Also, there are odd variations like list_feed_v3_calendar_sonarr_ics, list_wanted_cutoff, and list_wanted_missing that break the pattern, but overall the API tools are consistent.
With 234 tools, the server is massively over-tooled for the intended purpose of a Sonarr (TV show management) MCP. The count is extreme (over 50 tools), and many tools are simple CRUD operations for every resource type, leading to a bloated interface. Typical MCP servers should have 3-15 tools for focused tasks, and 234 tools is far beyond what an agent can effectively navigate.
The tool surface is extremely comprehensive—it covers full CRUD for most resources (series, episodes, episode files, quality profiles, etc.) plus many auxiliary operations like system management, backups, queue management, and manual imports. There are minor gaps like missing explicit get_episode_by_id (but there is list_episode with filters) or missing delete_episode (episodes are managed via series updates), but these are not critical dead ends. The completeness is high for the Sonarr domain, though the sheer volume means some operations are redundant.