qbittorrent-mcp
Allows management of a qBittorrent instance via its WebUI API, including listing torrents, inspecting properties and files, adding/pausing/resuming/deleting torrents, managing categories, tags, RSS feeds, and search plugins, and adjusting application settings.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@qbittorrent-mcplist all torrents currently downloading"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
qbittorrent-mcp
MCP server exposing qBittorrent's WebUI API v2 (qBittorrent >= 5.0) as tools, so an LLM can manage your torrents: list, inspect properties/trackers/files, add/pause/resume/delete torrents, manage categories, tags, RSS feeds and search plugins, and tweak application settings.
Built with FastMCP.
Enabling the API on your qBittorrent server
The WebUI API is enabled by default with the WebUI. You need WebUI access enabled (Tools > Preferences > WebUI) and one of two auth methods:
API key (qBittorrent >= v5.2.0 / WebAPI v2.14.1): generate one in Preferences > WebUI > API Key (format
qbt_<28 chars>). This is the recommended, stateless option.Username/password: the WebUI login you'd use in the browser. Works on all versions.
Related MCP server: LLMarr
Install
Download a wheel from the latest release
and install it as a uv tool (no repo checkout needed):
uv tool install qbittorrent_mcp-*.whlThis puts a qbittorrent-mcp command on your PATH. Register it with Claude Code:
claude mcp add qbittorrent \
--env QBITTORRENT_URL=http://localhost:8080 \
--env QBITTORRENT_API_KEY=<key> \
-- qbittorrent-mcpOr with username/password:
claude mcp add qbittorrent \
--env QBITTORRENT_URL=http://localhost:8080 \
--env QBITTORRENT_USERNAME=admin \
--env QBITTORRENT_PASSWORD=<password> \
-- qbittorrent-mcpFrom source
uv sync
cp .env.example .env # fill in QBITTORRENT_URL and an auth methodclaude mcp add qbittorrent \
--env QBITTORRENT_URL=http://localhost:8080 \
--env QBITTORRENT_API_KEY=<key> \
-- uv run --directory /path/to/qbittorrent-mcp qbittorrent-mcpConfig
Env var | Required | Default |
| yes | - |
| one of* | none (preferred) |
| one of* | none (fall-back) |
| one of* | none (fall-back) |
* You must set either QBITTORRENT_API_KEY or both QBITTORRENT_USERNAME and
QBITTORRENT_PASSWORD. If QBITTORRENT_API_KEY is set it wins; otherwise the
server logs in with the username/password on first use and reuses the session
cookie, re-authenticating automatically if it expires.
Tools
One tool per WebUI API endpoint, grouped by API section. Read-only GET endpoints are marked R; mutating POST endpoints are marked W; destructive ones (delete torrents, shutdown, remove categories/tags/rules/search jobs) are marked D and carry warnings in their docstrings.
Application
Tool | Endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Auth
Tool | Endpoint |
|
|
Log
Tool | Endpoint |
|
|
|
|
Sync
Tool | Endpoint |
|
|
|
|
Transfer
Tool | Endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Torrent management
Tool | Endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
qbittorrent_torrent_properties is the key observability tool: it returns
seeding_time, share_ratio, total_uploaded, save_path, and friends for a
single torrent hash.
RSS
Tool | Endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Search
Tool | Endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Write & destructive tools
Unlike tracearr-mcp, this server exposes qBittorrent's full read+write surface.
Destructive tools (qbittorrent_app_shutdown, qbittorrent_torrents_delete,
qbittorrent_rss_remove_item, qbittorrent_rss_remove_rule,
qbittorrent_search_delete) are annotated destructiveHint so clients can gate
them, and their docstrings call out the irreversible parts (e.g. delete_files
in qbittorrent_torrents_delete). Everything else that mutates state is a plain
write tool.
Notes
Many write tools take a
hashesargument: pass one hash, several separated by|, orallfor every torrent.qBittorrent 5.0 renamed a few endpoints versus 4.x: pause is
/torrents/stop, resume is/torrents/start, and rename torrent is/torrents/rename. This server targets qBittorrent >= 5.0.qbittorrent_torrents_addaccepts newline-separated magnet/URLs inurls, or a single base64-encoded.torrentfile intorrent_b64.API-key auth cannot hit
/auth/*endpoints (including logout) — qBittorrent rejects those, and the error is surfaced as-is.
Development
make help # list all commandsCommand | Does |
|
|
| Offline tests - one per endpoint, mocked HTTP |
| Tests against the live instance (needs |
| Build wheel + sdist into |
| Bump the version in |
| Remove build artifacts |
The release workflow (.github/workflows/release.yml) builds and publishes to
Releases whenever a v*
tag is pushed - so the usual flow is make bump-patch, commit, then tag and
push.
The integration suite is read-only and never modifies your qBittorrent instance.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceA comprehensive MCP server enabling LLMs to execute commands, manage files, interact with Figma, search the web, generate images, and more, extending their capabilities beyond text generation.Apache 2.0
- Alicense-qualityBmaintenanceAn MCP server that replicates Sonarr/Radarr/Lidarr functionality driven by an LLM, enabling automated torrent management for TV shows and movies.MIT
- Alicense-qualityCmaintenanceMCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.MIT
- AlicenseBqualityBmaintenanceMCP 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
Related MCP Connectors
MCP server exposing the Backtest360 engine API as tools for AI agents.
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SavageCore/qbittorrent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server