M
manueltarouca/qbt-kit
A client, CLI and MCP server for the qBittorrent WebUI API. All 123 endpoints, checked against qBittorrent's source.
SECURITY.md ✓
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"manueltarouca-qbt-kit": {
"command": "uvx",
"args": ["qbt-mcp"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"manueltarouca-qbt-kit": {
"command": "uvx",
"args": ["qbt-mcp"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio manueltarouca-qbt-kit -- uvx qbt-mcp
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 1 ★ · manueltarouca/qbt-kit · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 1 ★ · 23 个来源 · mcp
- 安装
uvx qbt-mcp
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
uvx qbt-mcp。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
manueltarouca/qbt-kit；我们收录于 2026-10-23；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# qbt-kit
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A complete, typed Python client for the qBittorrent WebUI API — with a CLI that
covers every endpoint one-to-one, and an MCP server so coding agents can drive
it without deleting your data.
$ qbt coverage
qbt-kit coverage — target release-5.2.3
scope n spec progress
torrents 61 61 ████████████████████ 61/61
app 16 16 ████████████████████ 16/16
rss 14 14 ████████████████████ 14/14
search 11 11 ████████████████████ 11/11
transfer 9 9 ████████████████████ 9/9
torrentcreator 4 4 ████████████████████ 4/4
auth 2 2 ████████████████████ 2/2
clientdata 2 2 ████████████████████ 2/2
log 2 2 ████████████████████ 2/2
sync 2 2 ████████████████████ 2/2
TOTAL 123 123 ████████████████████ 100.0%
The ledger is generated from qBittorrent's own source, and CI fails if it slips.
## Highlights
All 123 endpoints of qBittorrent 5.2.3, each one a spec entry that
generates the client method, the CLI command and the docs together.
A verifiable coverage claim. The endpoint list is extracted from the
qBittorrent C++ source per release tag and committed, so CI fails both when
the spec misses an endpoint and when it invents one.
An MCP server with 15 tools — 13 task-shaped, plus qbtcall and
listendpoints — and safety gates that hold even through the escape hatch.
Compatibility measured, not assumed — tested against real 4.6, 5.0, 5.1
and 5.2 containers, with a rename table so torrents/stop resolves to
pause on servers that predate the rename.
Typed throughout, no runtime dependency beyond httpx and typer.
That coverage claim is worth a sentence of context. The wiki page most clients
are written against documents 78 endpoints. qBittorrent 5.2.3 ships
123, and two whole scopes — torrentcreator and clientdata — appear in
no wiki page at all.
## Installation
PyPI's qbt name belongs to an unrelated package, so the CLI is run via
--from:
sh
uvx --from qbt-kit qbt doctor
uvx --from "qbt-kit[mcp]" qbt-mcp --help # the server lives in the mcp extra
Both run via --from because the qbt name on PyPI belongs to an unrelated
package, and qbt-mcp is a script inside this one rather than a package of its
own — uvx qbt-mcp resolves to nothing.
Or add it to a project:
sh
uv add qbt-kit # library and CLI
uv add "qbt-kit[mcp]" # with the MCP server
### As a Claude Code plugin
This repository is also a plugin marketplace, so one line installs the MCP
server and the skill together:
/plugin install qbt-kit --marketplace manueltarouca/qbt-kit
The bundled MCP server runs from the plugin's own checkout, so it needs uv
but not a published package, and it always matches the version you installed.
Point it at your server with QBTURL, and see Configuration
for credentials.
## Quickstart
sh
qbt doctor # version, auth mode, endpoint availability
qbt torrents info --category tv # the API calls this info, not list
qbt torrents add --urls --category tv --auto-tmm
qbt health # swarm health across the queue
qbt coverage # the endpoint coverage ledger
qbt call torrents/pieceStates -p hash= # raw, reaches all 123
Scope commands mirror the API exactly — torrents info, not a friendlier
list — so anything you read in qBittorrent's own docs translates directly.
--json works everywhere, so every command composes with jq.
covers every endpoint one-to-one, and an MCP server so coding agents can drive
it without deleting your data.
$ qbt coverage
qbt-kit coverage — target release-5.2.3
scope n spec progress
torrents 61 61 ████████████████████ 61/61
app 16 16 ████████████████████ 16/16
rss 14 14 ████████████████████ 14/14
search 11 11 ████████████████████ 11/11
transfer 9 9 ████████████████████ 9/9
torrentcreator 4 4 ████████████████████ 4/4
auth 2 2 ████████████████████ 2/2
clientdata 2 2 ████████████████████ 2/2
log 2 2 ████████████████████ 2/2
sync 2 2 ████████████████████ 2/2
TOTAL 123 123 ████████████████████ 100.0%
The ledger is generated from qBittorrent's own source, and CI fails if it slips.
## Highlights
All 123 endpoints of qBittorrent 5.2.3, each one a spec entry that
generates the client method, the CLI command and the docs together.
A verifiable coverage claim. The endpoint list is extracted from the
qBittorrent C++ source per release tag and committed, so CI fails both when
the spec misses an endpoint and when it invents one.
An MCP server with 15 tools — 13 task-shaped, plus qbtcall and
listendpoints — and safety gates that hold even through the escape hatch.
Compatibility measured, not assumed — tested against real 4.6, 5.0, 5.1
and 5.2 containers, with a rename table so torrents/stop resolves to
pause on servers that predate the rename.
Typed throughout, no runtime dependency beyond httpx and typer.
That coverage claim is worth a sentence of context. The wiki page most clients
are written against documents 78 endpoints. qBittorrent 5.2.3 ships
123, and two whole scopes — torrentcreator and clientdata — appear in
no wiki page at all.
## Installation
PyPI's qbt name belongs to an unrelated package, so the CLI is run via
--from:
sh
uvx --from qbt-kit qbt doctor
uvx --from "qbt-kit[mcp]" qbt-mcp --help # the server lives in the mcp extra
Both run via --from because the qbt name on PyPI belongs to an unrelated
package, and qbt-mcp is a script inside this one rather than a package of its
own — uvx qbt-mcp resolves to nothing.
Or add it to a project:
sh
uv add qbt-kit # library and CLI
uv add "qbt-kit[mcp]" # with the MCP server
### As a Claude Code plugin
This repository is also a plugin marketplace, so one line installs the MCP
server and the skill together:
/plugin install qbt-kit --marketplace manueltarouca/qbt-kit
The bundled MCP server runs from the plugin's own checkout, so it needs uv
but not a published package, and it always matches the version you installed.
Point it at your server with QBTURL, and see Configuration
for credentials.
## Quickstart
sh
qbt doctor # version, auth mode, endpoint availability
qbt torrents info --category tv # the API calls this info, not list
qbt torrents add --urls --category tv --auto-tmm
qbt health # swarm health across the queue
qbt coverage # the endpoint coverage ledger
qbt call torrents/pieceStates -p hash= # raw, reaches all 123
Scope commands mirror the API exactly — torrents info, not a friendlier
list — so anything you read in qBittorrent's own docs translates directly.
--json works everywhere, so every command composes with jq.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/manueltarouca-qbt-kit/)
- 来源
- awesome · https://github.com/manueltarouca/qbt-kit
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 该仓库根目录有
SECURITY.md（我们只核文件存在，未核内容）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。