prowlarr-mcp
Related Servers
Alternatives to prowlarr-mcp
No user-submitted related servers found.
Related Servers
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- FlicenseAqualityBmaintenanceMCP server to manage your *ARR media stack (Radarr, Sonarr, Lidarr, Readarr, Prowlarr) for searching, adding, and managing movies, TV shows, music, books, and indexers.1-
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables interaction with Sonarr, Radarr, and Prowlarr through their APIs, allowing management and queries via MCP over stdio.26 npmMIT
- AlicenseBqualityAmaintenanceMCP server that exposes qui's JSON REST API as tools for monitoring and managing qBittorrent instances, torrents, automations, cross-seeding, RSS, backups, and related services.12MIT
- AlicenseCqualityAmaintenanceMCP server exposing Radarr's v3 REST API as tools, enabling LLMs to read and manage movies, downloads, history, indexers, and more.100MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.MIT
TDQS
Scored across 10 tools
Many tools have narrowly specific purposes, but the presence of generic 'resource' tools (prowlarr_system, prowlarr_applications, etc.) that accept arbitrary operations creates overlap with the dedicated functions for each operation. Additionally, the sheer number of tools (over 100) makes it difficult to identify the correct one without careful reading.
Most tools follow a consistent verb_noun pattern (e.g., list_indexers, create_indexer, update_indexer), but the generic resource tools (prowlarr_system, prowlarr_applications, etc.) break this by being noun-only and requiring an operation parameter. Some minor deviations like 'restore_backup_upload' and 'download_release' are acceptable but add slight irregularity.
With approximately 115 tools, this server is massively oversized for its purpose. The tool count far exceeds the typical 3-15 range, making the surface overwhelming and difficult to navigate. Even though the stated count is 10, the actual list contains over a hundred tools, which is an extreme mismatch.
The tool set provides thorough coverage of the Prowlarr domain: system administration, applications, indexers, configuration, download clients, proxies, notifications, tags, search, and history. Each resource type has full CRUD operations plus test, bulk, and schema discovery tools, leaving no obvious gaps for core workflows.