profilarr-mcp
OfficialRelated Servers
Alternatives to profilarr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA locally-run, read-only MCP server that lets an LLM client diagnose a self-hosted *arr media stack by aggregating across Sonarr, Radarr, Prowlarr, qBittorrent, Tdarr, and Profilarr.25 PyPIApache 2.0
- AlicenseAqualityAmaintenanceMCP server exposing Prowlarr's API v1 as tools for managing indexers, applications, download clients, and more, including cross-indexer searches and system commands.10MIT
- AlicenseCqualityAmaintenanceMCP server exposing Radarr's v3 REST API as tools, enabling LLMs to read and manage movies, downloads, history, indexers, and more.100MIT
- 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

dashbrr-mcpofficial
AlicenseAqualityAmaintenanceMCP server exposing Dashbrr's REST API as tools, so an LLM can read and manage a dashbrr instance: configured services, per-service health, and summary panels for many apps. Write tools cover settings management, download-queue deletes, Overseerr approvals, UI preferences, and the Plex auth PIN flow.34MIT- AlicenseNot gradedqualityCmaintenanceMCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.MIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action: announcements (list/get), databases (CRUD+sync), backups (full lifecycle), jobs (status), health/status, arr instances (list), and settings. No two tools overlap in purpose; even status vs health are clearly separated as system overview vs health check.
The dominant pattern is profilarr_verb_noun (get_, list_, create_, update_, delete_, sync_, download_, upload_). However, profilarr_health and profilarr_status are noun-only, and get_openapi_spec is slightly inconsistent with list vs get. Minor deviations, but overall predictable and readable.
20 tools is on the heavier side but justified by the breadth of the domain: databases, backups, announcements, arr instances, jobs, health, and settings. Each tool serves a distinct function, so the count feels appropriate rather than bloated.
Core workflows are well covered: full CRUD for database links and backups, plus settings and status. Minor gaps exist (e.g., no arr instance add/remove/sync, no announcement management), but these are likely outside the server's primary scope. The surface is coherent for most user journeys.