Backing Platform — qBittorrent

qbittorrent-agent is a client of a qBittorrent WebUI (v2 API). This page provides a Docker recipe for deploying one locally to serve as the target of QBITTORRENT_URL. For production topologies, follow the upstream qBittorrent documentation and the LinuxServer image documentation.

Backing-system recipe

Each connector in the ecosystem follows the same convention — a docs/platform.md recipe for the system it integrates with, accompanied by a sample Compose stack that mirrors the upstream image. Systems offered only as a managed service have no local recipe.

Single-node deployment (Compose)

The widely used linuxserver/qbittorrent image runs the WebUI on :8080. The following stack provisions one qBittorrent instance with persistent configuration and downloads:

# docker/qbittorrent.compose.yml
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent@sha256:<digest>
    container_name: qbittorrent
    hostname: qbittorrent
    restart: unless-stopped
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
    ports:
      - "8080:8080"            # WebUI / v2 REST API
      - "6881:6881"            # BitTorrent (TCP)
      - "6881:6881/udp"        # BitTorrent (UDP)
    volumes:
      - qbittorrent_config:/config
      - qbittorrent_downloads:/downloads

volumes:
  qbittorrent_config:
  qbittorrent_downloads:

docker compose -f docker/qbittorrent.compose.yml up -d

# The temporary WebUI password is printed on first boot:
docker compose -f docker/qbittorrent.compose.yml logs | grep -i password

Connect qbittorrent-agent

export QBITTORRENT_URL=<configured-endpoint>
export QBITTORRENT_USERNAME=<configured-principal>
export QBITTORRENT_PASSWORD=<the-password-from-the-logs>
export TLS_PROFILE=private-pki
export TLS_PROFILES_REF=secret://runtime/tls-profiles

qbittorrent-mcp --transport streamable-http --host 0.0.0.0 --port 8000

Combined deployment

A combined stack places qBittorrent and the MCP server on one Docker network, so the server reaches the WebUI by container name:

# docker/stack.compose.yml
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent@sha256:<digest>
    hostname: qbittorrent
    environment:
      - PUID=1000
      - PGID=1000
      - WEBUI_PORT=8080
    ports: ["8080:8080"]
    volumes:
      - qbittorrent_config:/config
      - qbittorrent_downloads:/downloads

  qbittorrent-agent-mcp:
    image: example/qbittorrent-agent@sha256:<digest>
    depends_on: [qbittorrent]
    environment:
      - QBITTORRENT_URL=${QBITTORRENT_URL:?required}
      - QBITTORRENT_USERNAME=${QBITTORRENT_USERNAME:?required}
      - QBITTORRENT_PASSWORD=${QBITTORRENT_PASSWORD:?required}
      - TLS_PROFILE=private-pki
      - TLS_PROFILES_REF=secret://runtime/tls-profiles
      - TRANSPORT=streamable-http
      - HOST=0.0.0.0
      - PORT=8000
    ports: ["8000:8000"]

volumes:
  qbittorrent_config:
  qbittorrent_downloads:

docker compose -f docker/stack.compose.yml up -d

Manage qBittorrent from the agent

With the WebUI running and the connection variables set, the MCP tools drive torrent control, RSS automation, and search end to end — add and pause torrents, inspect transfer statistics, and configure RSS auto-download rules conversationally through the A2A agent.