qbittorrent-mcp
Related Servers
Alternatives to qbittorrent-mcp
No user-submitted related servers found.
Related Servers
- 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 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
- AlicenseNot gradedqualityBmaintenanceAn MCP server that replicates Sonarr/Radarr/Lidarr functionality driven by an LLM, enabling automated torrent management for TV shows and movies.MIT
- AlicenseAqualityAmaintenanceMCP server exposing autobrr's full API as tools, enabling LLMs to read and manage filters, indexers, feeds, clients, actions, releases, and system config. It wraps approximately 104 endpoints into 13 resource-scoped tools for comprehensive autobrr instance management.13MIT
- AlicenseBqualityAmaintenanceMCP server for rTorrent BitTorrent automation, enabling torrent management (add/list/pause/delete), multi-source searching (Nyaa, Pirate Bay, etc.), and post-processing workflows via natural language.71MIT
- FlicenseAqualityDmaintenanceEnables interaction with qBittorrent through its Web API to search for torrents using search plugins and manage downloads. Supports torrent searching, downloading via URLs/magnet links, and torrent management operations like pause, resume, and delete.73-
TDQS
Scored across 90 tools
Each tool targets a distinct resource and action, from torrent operations to RSS and search. Despite the large number, the combinations of domain and operation keep purposes clear, and descriptions remove any ambiguity.
All tools share the qbittorrent_<domain>_<action> prefix, which is consistent. However, actions mix nouns (properties, trackers) and verbs (list, pause), and getter/setter pairs are not uniformly marked (e.g., download_limit vs set_download_limit). The style is readable but not a single predictable pattern.
With 90 tools, this far exceeds the 'extreme' threshold of 50+ tools. While it mirrors the full qBittorrent WebUI API, the sheer number makes it overwhelming and impairs agent tool selection.
The tool set provides comprehensive coverage of qBittorrent functionality, including torrent lifecycle, file and tracker management, categories, tags, RSS feeds/rules, search plugins, transfer settings, and app preferences. No significant gaps are evident.