downloader-mcp
Enables interaction with SABnzbd (usenet) and qBittorrent (torrent) download clients through their APIs. Each client is optional and only tools for configured clients are registered.
README
downloader-mcp
An MCP server for download clients —
SABnzbd (usenet) and qBittorrent (torrents) — packaged as a
Docker container. Companion to media-management MCPs like
servarr-mcp.
Each client is optional: configure only the ones you actually run, and only those tools register.
Tools
SABnzbd (usenet)
| Tool | Description |
|---|---|
sabnzbd_queue |
Current download queue with speeds and ETAs |
sabnzbd_history |
Recent history (newest first) |
sabnzbd_categories |
Configured categories |
sabnzbd_version |
SABnzbd version info |
qBittorrent (torrents)
| Tool | Description |
|---|---|
qbittorrent_list_torrents |
List torrents, optional status filter |
qbittorrent_get_torrent |
Torrent details by info-hash |
qbittorrent_torrent_files |
Files inside a torrent |
qbittorrent_transfer_info |
Global transfer stats |
qbittorrent_categories |
Configured categories |
qbittorrent_version |
qBittorrent application version |
Configuration
Each client requires its full config block to enable; partial config silently disables the client.
| Client | Required env vars | Default port |
|---|---|---|
| SABnzbd | SABNZBD_URL, SABNZBD_API_KEY |
8080 |
| qBittorrent | QBITTORRENT_URL, QBITTORRENT_USERNAME, QBITTORRENT_PASSWORD |
8080 |
API keys / credentials are found in each app's settings:
- SABnzbd: Config → General → API Key
- qBittorrent: Tools → Options → Web UI (default user
admin)
Note: SABnzbd and qBittorrent both default to port 8080. If you run both on the same host, remap one of them in its own config.
At least one client must be configured or the server exits with an error.
Run with Docker
docker build -t downloader-mcp .
docker run -i --rm \
-e SABNZBD_URL=http://192.168.1.50:8080 -e SABNZBD_API_KEY=... \
-e QBITTORRENT_URL=http://192.168.1.50:8081 \
-e QBITTORRENT_USERNAME=admin -e QBITTORRENT_PASSWORD=... \
downloader-mcp
Published image
After each push to main, GitHub Actions builds and pushes a multi-arch
image to GHCR:
ghcr.io/carldog/downloader-mcp:latest (linux/amd64 + linux/arm64)
Pull instead of building locally:
docker pull ghcr.io/carldog/downloader-mcp:latest
docker run -i --rm \
-e SABNZBD_URL=... -e SABNZBD_API_KEY=... \
ghcr.io/carldog/downloader-mcp:latest
Run with Docker Compose (HTTP, long-lived)
The compose file runs the server in HTTP mode (Streamable HTTP) for
long-lived deployment via Portainer or Compose. It pulls the published
image from ghcr.io/carldog/downloader-mcp:latest.
# Set whichever client credentials apply:
export SABNZBD_URL=http://192.168.1.50:8080; export SABNZBD_API_KEY=...
export QBITTORRENT_URL=http://192.168.1.50:8081
export QBITTORRENT_USERNAME=admin; export QBITTORRENT_PASSWORD=...
export HOST_PORT=3003 # optional, defaults to 3003
docker compose up
The MCP endpoint will be at http://<host>:${HOST_PORT}/mcp.
Deploy via Portainer (Stack from Git)
- In Portainer, Stacks → Add Stack → Repository.
- Repository URL:
https://github.com/CarlDog/downloader-mcp - Compose path:
docker-compose.yml - Environment variables: set whichever client credentials apply, plus
optionally
HOST_PORT. - Deploy. Healthcheck reaches green within ~10 seconds.
Use with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"downloader": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "SABNZBD_URL", "-e", "SABNZBD_API_KEY",
"-e", "QBITTORRENT_URL",
"-e", "QBITTORRENT_USERNAME", "-e", "QBITTORRENT_PASSWORD",
"downloader-mcp"
],
"env": {
"SABNZBD_URL": "http://192.168.1.50:8080",
"SABNZBD_API_KEY": "...",
"QBITTORRENT_URL": "http://192.168.1.50:8081",
"QBITTORRENT_USERNAME": "admin",
"QBITTORRENT_PASSWORD": "..."
}
}
}
}
Drop the -e/env entries for whichever client you don't run.
Local development
npm install
cp .env.example .env # then edit
SABNZBD_URL=... SABNZBD_API_KEY=... npm run dev
Security
- Container runs as a non-root user (
mcp). - Credentials passed via env vars — never baked into the image.
- A
.githooks/pre-commitruns gitleaks (secrets) and a PII pattern check (user-home paths, personal-domain emails). Activate it once per clone:git config core.hooksPath .githooks.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。