MCP server for terminal commands, file operations, and process management
qBittorrent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
qBittorrent MCP server: eleven intent-shaped tools, multi-instance, version-aware calls.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user zxw060810-qbittorrent-mcp '--' uvx qb-mcp
# 2 — ask your agent for something these tools do
# qb_instances, qb_overview, qb_list and 8 more
qBittorrent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts qBittorrent as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user zxw060810-qbittorrent-mcp '--' uvx qb-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List every configured qBittorrent instance and whether it is reachable.
Takes no parameters.
Global status for one instance, or all instances when omitted.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | no | instance key from .instances.json; empty means every instance. |
List torrents on one instance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| filter | string | no | all | downloading | seeding | completed | paused | active | stalled | errored. |
| category | string | no | restrict to a category name. |
| sort | string | no | field to sort by, e.g. uploaded, ratio, added_on, size. |
| limit | integer | no | maximum rows to return (1-50). |
Show one torrent in depth, including tracker status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| hash | string | no | torrent hash (preferred). |
| name | string | no | fuzzy name match, used when hash is empty. |
| show_tracker_urls | boolean | no | reveal full announce URLs (they may contain a private tracker passkey - off by default so the secret never reaches the model). |
Explain why a qBittorrent instance is (or is not) uploading.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| hash | string | no | optional torrent hash to inspect trackers for a single torrent. |
Change torrent state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| action | string | yes | pause | resume | reannounce | force_start. |
| hashes | array | no | torrent hashes; empty means every torrent. |
Set upload/download speed limits in bytes per second (0 = unlimited).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| up | integer | no | upload limit in bytes/s; 0 means unlimited. |
| dl | integer | no | download limit in bytes/s; 0 means unlimited. |
| hashes | array | no | torrent hashes; empty means the global limit. |
| mode | string | no | "normal" for the normal global limit, "alternative" for the alternative (scheduled) limit. qBittorrent keeps them separate and the active one depends on whether alternative mode is switched on. |
Set ratio and/or seeding-time limits for specific torrents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| hashes | array | yes | torrent hashes to update. |
| ratio | number | no | maximum ratio; -1 means unlimited, -2 means use the global value. |
| seeding_time | integer | no | maximum seeding time in MINUTES (qBittorrent's unit); -1 unlimited, -2 use global (default). |
| inactive_seeding_time | integer | no | maximum inactive seeding time in MINUTES; -1 unlimited, -2 use global (default). |
| action | string | no | what to do once a limit is reached - "stop" (default) or "enable_super_seeding". Removal is deliberately not offered here; use qb_remove for anything destructive. |
| mode | string | no | how the limits combine - "default" (inherit), "any" (stop when either limit is reached) or "all" (both). Only qBittorrent 5.3+ honours it; older versions ignore the field. |
Add a torrent from a URL, magnet link, or a local .torrent path.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| source | string | yes | magnet link, http(s) URL, or absolute path to a .torrent file. |
| savepath | string | no | target directory; empty uses the instance default. |
| category | string | no | category to assign. |
| paused | boolean | no | add in paused state (default true) so it can be reviewed first. |
| wait_seconds | number | no | how long to wait for the torrent to show up. Magnet links ingest metadata asynchronously, so the add request returning 200 does not prove anything; the torrent must appear in the list. |
Remove torrents. Downloaded files are kept unless delete_files is true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| hashes | array | yes | torrent hashes to remove. |
| delete_files | boolean | no | also delete the downloaded data (default false). |
Assign a category and/or tags to torrents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance | string | yes | instance key from .instances.json. |
| hashes | array | yes | torrent hashes to update. |
| category | string | no | category name; empty leaves it unchanged. |
| tags | array | no | tags to add. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install qBittorrent or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| qb_instances | no tags | |
| qb_overview | no tags | |
| qb_list | no tags | |
| qb_detail | no tags | |
| qb_diagnose | no tags | |
| qb_control | no tags | |
| qb_set_limit | untrusted-inputexternal-sink | untrusted-input: keyword "download"; external-sink: handler sends an HTTP POST ( qb.post("/api/v2/torrents/setUploadLimit") at src/qb_mcp/server.py:628, handler sends an HTTP POST ( qb.post("/api/v2/torrents/setDownloadLimit") at src/qb_mcp/server.py:633, handler sends an HTTP POST ( qb.post("/api/v2/transfer/setUploadLimit") at src/qb_mcp/server.py:642 |
| qb_set_share | external-sink | external-sink: handler sends an HTTP POST ( qb.post("/api/v2/torrents/setShareLimits") at src/qb_mcp/server.py:831 |
| qb_add | external-sink | external-sink: handler sends an HTTP POST ( qb.post("/api/v2/torrents/add") at src/qb_mcp/server.py:904, handler sends an HTTP POST ( qb.post("/api/v2/torrents/add") at src/qb_mcp/server.py:912 |
| qb_remove | no tags | |
| qb_category | external-sink | external-sink: handler sends an HTTP POST ( qb.post("/api/v2/torrents/setCategory") at src/qb_mcp/server.py:989, handler sends an HTTP POST ( qb.post("/api/v2/torrents/addTags") at src/qb_mcp/server.py:991 |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.4. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish qBittorrent can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.