transmission-mcp
Allows an agent to send magnet links to a Transmission daemon and monitor downloads, including adding magnets (with optional download directory and paused state) while validating and detecting duplicates, checking per-torrent status with verdicts like downloading, stalled, fetching_metadata, queued, checking, paused, complete, seeding, and error alongside progress, speed, peers, and ETA, listing torrents filtered by verdict, and pausing or resuming torrents.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@transmission-mcpadd this magnet link and tell me when it's done: magnet:?xt=urn:btih:0123456789abcdef"
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.
transmission-mcp
MCP server (streamable HTTP, /mcp on port 8650) that lets an agent send magnet links to
Transmission and check whether they are downloading.
Tools
add_magnet(magnet, download_dir?, paused?): validates the magnet, adds it, reports duplicates.get_torrent_status(hash_or_id): verdict (downloading,stalled,fetching_metadata,queued,checking,paused,complete,seeding,error) plus progress, speed, peers, ETA.list_torrents(verdict?)pause_torrent(hash_or_id)/resume_torrent(hash_or_id)
Related MCP server: Transmission MCP Server
Config (environment)
Variable | Default |
|
|
| unset (no auth) |
|
|
Quick start
Both methods serve the MCP endpoint at http://127.0.0.1:8650/mcp. You need a reachable
Transmission RPC endpoint (set TRANSMISSION_URL); .env.example lists the variables.
Option 1: Docker Compose
cp .env.example .env # edit TRANSMISSION_URL / credentials
docker compose up --buildNo Transmission yet? Start a bundled one alongside (web UI on http://127.0.0.1:9091,
downloads in ./downloads):
docker compose --profile transmission up --buildWith the bundled daemon, set TRANSMISSION_URL=http://transmission:9091/transmission/rpc
(the default).
Option 2: Run Python directly
Requires Python 3.11+.
With uv:
uv sync
TRANSMISSION_URL=http://127.0.0.1:9091/transmission/rpc uv run transmission-mcpWith plain pip:
python -m venv .venv && . .venv/bin/activate
pip install .
TRANSMISSION_URL=http://127.0.0.1:9091/transmission/rpc transmission-mcpDevelop
uv sync && uv run pytest
uv run transmission-mcpContainer (Podman)
podman build -t localhost/transmission-mcp:latest .The Quadlet unit lives in the hermes-desktop repo (quadlet/transmission-mcp.container), joins the
hermes pod, and is reached by Hermes at http://127.0.0.1:8650/mcp. There is no auth; do not expose the port.
This server cannot be deployed
Maintenance
Related MCP Connectors
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Task management for teams building with AI agents. Agents claim tasks and report progress.
Hosted coding agent: start, follow up on and stop tasks that can open GitHub pull requests.
Manage Superlist tasks and lists in plain language from any MCP-compatible AI agent.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceA service that provides programmatic access to qBittorrent's WebUI API, enabling management of torrents, trackers, tags, speed controls, and system information through natural language.29-
- AlicenseNot gradedqualityDmaintenanceProvides tools for interacting with the Transmission BitTorrent client via natural language, enabling users to manage torrents, configure download settings, and monitor download activity.2MIT
- FlicenseAqualityDmaintenanceEnables interaction with qBittorrent through its Web API to search for torrents using search plugins and manage downloads. Supports torrent searching, downloading via URLs/magnet links, and torrent management operations like pause, resume, and delete.73-
- FlicenseNot gradedqualityDmaintenanceEnables controlling a Transmission torrent daemon, allowing adding, listing, controlling torrents and checking free space, with support for SOCKS5 proxy for remote access.-