"qbittorrent" matching MCP servers:

MCP server exposing qBittorrent's WebUI API v2 as tools, enabling LLMs to manage torrents, categories, tags, RSS feeds, search plugins, and application settings.

A service that provides programmatic access to qBittorrent's WebUI API, enabling management of torrents, trackers, tags, speed controls, and system information through natural language.

Enables control of a qBittorrent instance via its WebUI API, supporting torrent management, category management, and transfer information with cookie-session authentication.

Enables interaction with SABnzbd (usenet) and qBittorrent (torrent) download clients through their APIs. Each client is optional and only tools for configured clients are registered.

A client, CLI and MCP server for the qBittorrent WebUI API, covering all 123 endpoints on qBittorrent 5.2.3. Destructive operations require confirmation, and read-only mode blocks every mutating endpoint, including through the raw call.

MCP 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.

MCP server for media stack management — movies/TV, audiobooks/ebooks, and music. Integrates with Jellyseerr, Radarr, Sonarr, Jellyfin, Prowlarr, qBittorrent, Audiobookshelf, and Navidrome.

A remote MCP server for managing your arr stack (Sonarr, Radarr, qBittorrent, Seerr) via Claude.ai on mobile, enabling you to fix bad downloads, block release groups, request new content, and check trending.

MCP 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.