autobrr-mcp
Related Servers
Alternatives to autobrr-mcp
No user-submitted related servers found.
Related Servers
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- AlicenseAqualityAmaintenanceMCP server exposing qBittorrent's WebUI API v2 as tools, enabling LLMs to manage torrents, categories, tags, RSS feeds, search plugins, and application settings.902MIT
- AlicenseAqualityBmaintenanceMCP server exposing qbit_manage's Web API as tools, so an LLM can read and manage a qbit_manage instance: run maintenance commands on qBittorrent torrents, manage config files, scheduler, logs, security settings, and system state.6MIT
- AlicenseBqualityAmaintenanceMCP server exposing Seerr's full v1 REST API as tools, enabling LLMs to search and discover media, manage requests and approvals, users, issues, watchlists, and integration settings for Plex/Jellyfin/Emby and Sonarr/Radarr, including reads and writes with destructive operations flagged.151MIT
- 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
- AlicenseCqualityAmaintenanceMCP server exposing Radarr's v3 REST API as tools, enabling LLMs to read and manage movies, downloads, history, indexers, and more.100MIT
TDQS
Scored across 13 tools
Each of the 13 tools targets a distinct autobrr resource domain (actions, filters, indexers, IRC, feeds, download clients, lists, notifications, API keys, proxies, releases, config, system). The operation lists within each tool are clearly scoped, so there is no ambiguity about which tool to use.
All tool names follow a consistent autobrr_<resource> pattern using snake_case, and operations within each tool use a uniform verb_noun structure (create_, list_, update_, delete_). No naming conventions are mixed.
13 tools is an ideal size for an autobrr management server. Each tool covers a meaningful resource category without unnecessary overlap or bloat, making the set well-scoped and easy to navigate.
The tool set provides comprehensive lifecycle coverage for most resources, including CRUD, testing, and operational actions. Minor gaps exist (e.g., no update/delete for IRC channels, no single-action fetch), but these do not create dead ends and are easily workable.