No user-submitted related servers found.
Scored across 237 tools
The tool names follow a CRUD-resource pattern, but there are multiple clusters like create_downloadclient, create_downloadclient_test, create_downloadclient_testall, and create_downloadclient_action_by_name that share the identical description 'Create DownloadClient.' Generic static-resource tools such as get_by_path, get_content_by_path, and list_root also blur boundaries.
Most tools use a consistent verb_noun pattern: create_*, list_*, get_*_by_id, update_*, and delete_*. Exceptions like update_qualitydefinition_update, create_system_restart, get_mediacover_by_movie_id_by_filename, and the static-resource passthroughs break the pattern but are not pervasive.
237 tools is an extreme count for an MCP server, far beyond the 3-15 well-scoped range. Even though Radarr has a large API, exposing essentially every route as an individual tool will overwhelm an agent's tool-selection capacity.
The surface covers Radarr's core domain thoroughly: movie and movie-file lifecycle, lookup, queue, history, blocklist, import lists, indexers, download clients, notifications, profiles, custom formats, quality definitions, tags, root folders, and system administration. There are no obvious dead ends for the stated media-management purpose.