qb-mcp
Related Servers
Alternatives to qb-mcp
No user-submitted related servers found.
Related Servers
- 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-
- FlicenseNot gradedqualityDmaintenanceA service that provides programmatic access to qBittorrent's WebUI API, enabling management of torrents, trackers, tags, speed controls, and system information through natural language.29-
- AlicenseNot gradedqualityCmaintenanceEnables an agent to submit magnet links to a Transmission daemon and monitor their download progress, including pausing, resuming, and listing torrents with verdicts like downloading, stalled, or complete.MIT
- AlicenseAqualityCmaintenanceMCP server exposing qBittorrent's WebUI API v2 as tools, enabling LLMs to manage torrents, categories, tags, RSS feeds, search plugins, and application settings.903MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools for interacting with the Transmission BitTorrent client via natural language, enabling users to manage torrents, configure download settings, and monitor download activity.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables an agent to run a whole home media stack — Plex, Sonarr, Radarr, Prowlarr, qBittorrent, and Bazarr — by conversation: requesting shows and films, seeing what's downloading, fixing stuck torrents, getting recommendations, and freeing disk space. A deterministic background watch loop keeps downloads moving and alerts you only to what it can't fix, with gated deletes and a 7-day undo.MIT
TDQS
Scored across 11 tools
Most tools target clearly separate actions: add/remove torrents, list/detail, control state, set limits, set share limits, assign categories. The only real overlap is in instance-level inspection, where qb_instances (reachability), qb_overview (global status) and qb_diagnose (why it is not uploading) all report on the same instance health, though the descriptions draw workable boundaries between them.
Every tool uses a uniform qb_ prefix with snake_case, which makes the set immediately readable and filterable. The suffix style is slightly mixed (verb-like qb_add/qb_remove/qb_list versus noun-like qb_detail/qb_category/qb_overview), but within this namespace the pattern is predictable rather than chaotic.
Eleven tools is well within the ideal band for a qBittorrent management server. Each tool maps to a distinct operational concern (discovery, ingestion, removal, organisation, inspection, diagnostics, state control, rate limits, seeding rules) with no filler entries.
The surface covers the full torrent lifecycle: add, list, detail, categorise/tag, pause/resume/reannounce, remove, plus speed and share-limit tuning and a diagnostic path. Minor gaps remain around per-file inspection and priority setting, forced recheck, queue position, and creating/managing categories themselves, but these are workarounds rather than dead ends for most workflows.