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.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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: qBittorrent 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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Send files and manage client uploads from a compatible AI agent.
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Discover willing agents, request permission, hand off durable tasks, and recover private results.
Agent file transfer. No API key to start; price downloads in USDC on Base.
Related MCP Servers
- 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.4MIT
- 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.-
- AlicenseAqualityBmaintenanceEnables driving a Transmission daemon from Claude.ai and Claude Code, exposing every RPC method as a tool for torrent, session, queue, and bandwidth management across both protocol generations.27MIT