What can you do with this server?

This server exposes qui's REST API as MCP tools for monitoring and managing qBittorrent instances, torrents, and related services. * Authentication & API Keys: Check setup, get current user, validate sessions, change passwords, manage general and client API keys. * External Programs: List, create, update, delete, and execute external programs. * Notifications: List events; create, update, delete, and test notification targets. * ARR Integrations: Manage ARR instances (list/create/get/update/delete/test), test connections, resolve ARR data; manage tracker customizations. * Dashboard & UI: Get/update dashboard settings, filter views, custom themes, tracker icons. * Logging & System Info: Log settings/exclusions, list log files; version/application info. * Torrents & Cross-Seeding: List cross-instance torrents; cross-seed operations: status, apply, webhook checks, analyze, search, apply search; manage settings, triggers, blocklist, runs, completion, season packs. * Directory Scanning: Get/update settings; manage scan directories; trigger/cancel scans; view status, runs, injections, files; reset/requeue no-match. * Torznab: Manage indexers, discover, get health and tracker domains.

Which integrations are available for this server?

Provides tools for monitoring and managing qBittorrent instances, torrents, categories, tags, preferences, and automations. Provides tools for managing RSS feeds and automation related to torrent fetching and cross-seeding.

How do I use qui-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@qui-mcp What torrents are 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.

qui-mcp

by arr-mcps

Overview Schema Source Related Servers Discussions Admin

Python

Remote

qui-mcp

Part of the arr-mcps collection. MCP server exposing qui's JSON REST API as tools for monitoring and managing qBittorrent instances, torrents, automations, cross-seeding, RSS, backups, and related services.

Built with FastMCP. The initial release mirrors the full JSON API route surface as one MCP tool per endpoint.

Install

uv tool install qui_mcp-*.whl

claude mcp add qui \
  --env QUI_URL=https://your-qui-host \
  --env QUI_API_KEY=<api-key> \
  -- qui-mcp

From source:

uv sync
claude mcp add qui \
  --env QUI_URL=https://your-qui-host \
  --env QUI_API_KEY=<api-key> \
  -- uv run --directory /path/to/qui-mcp qui-mcp

Related MCP server: qbittorrent-mcp

Configuration

Env var	Required	Description
`QUI_URL`	yes	qui host, optionally including a reverse-proxy base path; `/api` is appended automatically
`QUI_API_KEY`	no	API key sent as `X-API-Key`; omit only when qui authentication is intentionally disabled

Create API keys in qui under Settings -> API Keys. The server never logs the key and sends no authentication header when it is unset.

Tools

12 resource-scoped tools, each covering multiple qui JSON endpoints (214 total) via an operation parameter: instances, torrents, categories, tags, preferences, automations, RSS, backups, orphan scans, cross-seed, Torznab, ARR integrations, notifications, API-key management, logs, and application metadata. Call a tool with operation set to one of its listed routes and an arguments object matching that route's parameters — the tool's own description (visible to your MCP client) lists every route and its method + path. This keeps the full REST surface available while costing a fraction of the context budget of registering all 214 routes as separate tools.

Tool	Routes
`qui_system`	55
`qui_cross_seed`	29
`qui_torrents`	24
`qui_torznab`	20
`qui_instances`	17
`qui_dir_scan`	15
`qui_rss`	14
`qui_automations`	12
`qui_backups`	10
`qui_categories_tags`	7
`qui_orphan_scan`	7
`qui_torrent_creator`	4

Streaming endpoints and binary downloads are intentionally omitted because MCP tool results are structured JSON values. Session-creation endpoints (/auth/setup, /auth/login, and /auth/logout) are also omitted; use qui's web UI for those flows.

Every tool accepts operation (the route name, e.g. qui_list_torrents) plus one optional arguments object:

{
  "operation": "qui_list_torrents",
  "arguments": {
    "instanceID": 1,
    "hash": "torrent-info-hash",
    "params": {"filter": "downloading"},
    "body": {"value": "request payload"}
  }
}

Path variables use their documented names. Query values belong in arguments.params and JSON request payloads belong in arguments.body.

Development

make help
make sync
make test
make build

make test uses only httpx.MockTransport. Live smoke tests require QUI_URL and can be run with make test-integration.

The release workflow builds a wheel and source distribution when a v* tag is pushed. Start at version 0.0.0; use make bump-patch, commit, tag, and push for the first release.

Available Tools

12 tools

qui_automationsB

qui automations operations on qui. Pass operation and an arguments object; path variables go directly in arguments, query values in arguments.params, and a JSON request body in arguments.body.

qui_apply_automations: POST /instances/{instanceID}/automations/apply
qui_create_automation: POST /instances/{instanceID}/automations/
qui_delete_automation: DELETE /instances/{instanceID}/automations/{ruleID}
qui_delete_automation_activity: DELETE /instances/{instanceID}/automations/activity
qui_dry_run_automations: POST /instances/{instanceID}/automations/dry-run
qui_get_automation_activity_run: GET /instances/{instanceID}/automations/activity/{activityId}
qui_list_automation_activity: GET /instances/{instanceID}/automations/activity
qui_list_automations: GET /instances/{instanceID}/automations/
qui_preview_automation_delete: POST /instances/{instanceID}/automations/preview
qui_reorder_automations: PUT /instances/{instanceID}/automations/order
qui_update_automation: PUT /instances/{instanceID}/automations/{ruleID}
qui_validate_automation_regex: POST /instances/{instanceID}/automations/validate-regex