qbittorrent-agent¶
qBittorrent management MCP Server + A2A Agent for the agent-utilities ecosystem — typed, deterministic tools for torrent control, RSS automation, and search over the qBittorrent WebUI API.
Official documentation
This site is the canonical reference for qbittorrent-agent, maintained alongside
every release.
Overview¶
qbittorrent-agent wraps the qBittorrent WebUI v2 REST API with typed,
deterministic MCP tools, and ships a companion Pydantic-AI A2A agent server. It
provides:
QbittorrentApi— a session-authenticated REST facade over the qBittorrent WebUI, composed from per-domain sub-clients (app, log, sync, transfer, torrents, RSS, search).- Seven action-dispatch MCP tools —
qbittorrent_app,qbittorrent_log,qbittorrent_sync,qbittorrent_transfer,qbittorrent_torrents,qbittorrent_rss, andqbittorrent_search, each individually toggled by an environment switch. - An A2A agent server (
qbittorrent-agent) that calls the MCP tool surface for conversational and multi-step torrent workflows.
Explore the documentation¶
- Installation — pip, source, extras, and the prebuilt Docker image.
- Deployment — run the MCP server and A2A agent, Docker Compose, Caddy + Technitium.
- Usage — the MCP tools, the
QbittorrentApiclient, and the CLI entry points. - Backing Platform — deploy qBittorrent with Docker.
- Architecture — agent, MCP server, layered client.
- Concepts — the
CONCEPT:QBT-*registry.
Quick start¶
Connect it to a qBittorrent instance:
export QBITTORRENT_URL=http://your-qbittorrent:8080
export QBITTORRENT_USERNAME=admin
export QBITTORRENT_PASSWORD=your_password
qbittorrent-mcp --transport streamable-http --host 0.0.0.0 --port 8000
See Installation and Deployment for the full matrix (PyPI extras, Docker image, all transports, the A2A agent, reverse proxy, DNS).