A simple MCP server for controlling your Transmission torrent daemon. Supports both direct connection and SOCKS5 proxy for remote access.
Most file and storage access work still happens through a UI a human drives. Transmission MCP server moves it into the conversation instead. A simple MCP server for controlling your Transmission torrent daemon. Supports both direct connection and SOCKS5 proxy for remote access.
The server publishes 5 tools. What each one is for:
add_torrent — Add a new torrent via magnet link or URL. - magnet_or_url: Magnet link or torrent file URL - download_dir: Optional custom download directory -control_torrent — Start, stop, or remove torrents. - action: "start", "stop", or "remove" - torrent_ids: Array of torrent IDs - delete_data: Whether to delete localget_free_space — Check available disk space for downloads. - path: Optional directory path to check - use_socks5: Use SOCKS5 proxy for this request (default: false)list_torrents — List all torrents with their status, progress, and download directories. - use_socks5: Use SOCKS5 proxy for this request (default: false)get_session_info — Get information about the Transmission daemon session, including version, settings, and statistics. - use_socks5: Use SOCKS5 proxy for this requestSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Configuration is passed through the environment: TRANSMISSION_HOST, TRANSMISSION_PORT, TRANSMISSION_USERNAME, TRANSMISSION_PASSWORD, USE_SOCKS5, SOCKS5_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Transmission's toolset — add_torrent, control_torrent, get_free_space and 2 more — is a fair guide to whether it matches your workflow. It is maintained by v-odoo-testing; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| add_torrent | Add a new torrent via magnet link or URL. - magnet_or_url: Magnet link or torrent file URL - download_dir: Optional custom download directory - use_socks5: Use SOCKS5 proxy for this request (default: false) |
| control_torrent | Start, stop, or remove torrents. - action: "start", "stop", or "remove" - torrent_ids: Array of torrent IDs - delete_data: Whether to delete local data when removing (default: false) - use_socks5: Use SOCKS5 proxy for th |
| get_free_space | Check available disk space for downloads. - path: Optional directory path to check - use_socks5: Use SOCKS5 proxy for this request (default: false) |
| list_torrents | List all torrents with their status, progress, and download directories. - use_socks5: Use SOCKS5 proxy for this request (default: false) |
| get_session_info | Get information about the Transmission daemon session, including version, settings, and statistics. - use_socks5: Use SOCKS5 proxy for this request (default: false) |
| Variable | Description | Required |
|---|---|---|
| TRANSMISSION_HOST | Endpoint or connection string the server talks to. | Optional |
| TRANSMISSION_PORT | Configuration value read at startup. | Optional |
| TRANSMISSION_USERNAME | Configuration value read at startup. | Optional |
| TRANSMISSION_PASSWORD | Configuration value read at startup. | Optional |
| USE_SOCKS5 | Configuration value read at startup. | Optional |
| SOCKS5_HOST | Endpoint or connection string the server talks to. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.