lidarr-mcp
Related Servers
Alternatives to lidarr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceMCP server exposing Radarr's v3 REST API as tools, enabling LLMs to read and manage movies, downloads, history, indexers, and more.100MIT
- AlicenseBqualityCmaintenanceMCP server that provides LLM tools to interact with Lyrion Music Server (LMS), enabling player control, playback management, playlist operations, and music library search.5524 npmMIT
- 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.MIT

profilarr-mcpofficial
AlicenseAqualityAmaintenanceMCP server exposing Profilarr's v1 REST API as tools, enabling an LLM to inspect and manage linked databases, connected Radarr/Sonarr instances, backups, jobs, announcements, and system status.20MIT- 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
- AlicenseNot gradedqualityCmaintenanceMCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.MIT
TDQS
Scored across 15 tools
While many tools clearly name their resource and action, the presence of generic dispatcher tools (e.g., lidarr_media_library, lidarr_release_search) that accept arbitrary operation strings creates significant overlap with the specific tools. The many 'action_' tools for providers are also underspecified, making it hard for an agent to know what to pass.
The naming mostly follows a consistent lidarr_verb_noun pattern, with clear verbs like list, get, create, update, delete. However, the dispatcher tools and some unique operations (reorder, action, test_all) break the pattern, and there are occasional oddities like get_system_routes_duplicate.
The server exposes over 200 tools (despite the stated count of 15), which is far too many for an agent to navigate effectively. This violates the well-scoped principle and makes the set difficult to use coherently.
The tool set provides broad coverage of Lidarr's functionality—from artist and album management to download queue, history, configuration, and system operations. CRUD operations are present for nearly every resource, and there are few obvious missing operations that would prevent an agent from accomplishing tasks.