No user-submitted related servers found.
Scored across 61 tools
Most tools have clearly distinct resources or actions, and the descriptions differentiate pairs like list_movies/get_movie and get_history/get_movie_history well. However, singular/bulk pairs such as update_movie/edit_movies and delete_movie/delete_movies could still be confused without carefully reading the descriptions.
The server overwhelmingly follows a snake_case verb_noun pattern, with list_/get_/add_/delete_/remove_ used predictably. Minor deviations like update_movie vs edit_movies, create_tag vs add_movie, and mixing delete_ with remove_ keep it from being perfectly consistent.
61 tools is far beyond the typical well-scoped MCP surface and exceeds the extreme-mismatch threshold. Even for a complex application like Radarr, exposing nearly every endpoint as a separate tool creates a bloated surface where many list, test, and config tools could be consolidated.
Core Radarr workflows are thoroughly covered, including movie CRUD, queue and file handling, release searching/grabbing, history, wanted, blocklist, commands, and system diagnostics. Minor gaps exist around full admin CRUD for indexers, download clients, import lists, notifications, and quality profiles, which are only list/test rather than fully manageable.