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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.