transmission-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSMISSION_URL | No | The URL of the Transmission instance (Default: http://localhost:9091). | http://localhost:9091 |
| TRANSMISSION_PASS | No | The password for Transmission authentication (optional). | |
| TRANSMISSION_USER | No | The username for Transmission authentication (optional). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_session | Get Transmission session configuration and version info. |
| get_session_statsA | Get session statistics (speeds, torrent counts, cumulative stats). |
| free_spaceA | Get free disk space in bytes at the specified path. |
| list_torrents | List all torrents with their details. |
| get_torrent_detailsB | Get detailed info for a specific torrent by its ID or hash. |
| get_torrent_statsC | Get stats and status for a specific torrent by its ID or hash. |
| get_recently_activeA | Get recently active torrents and IDs of recently removed ones. |
| add_torrentB | Add a torrent from magnet link, HTTP URL, or local file path. |
| remove_torrentC | Remove a torrent. Set delete_data=True to also delete downloaded files. |
| start_torrentC | Start (resume) a torrent. |
| stop_torrent | Stop (pause) a torrent. |
| verify_torrent | Verify torrent data integrity. |
| reannounce_torrent | Reannounce torrent to trackers. |
| move_torrentC | Move torrent data to a new location. |
| set_torrent_labelsC | Set labels for a torrent. |
| download_torrent | Download a torrent from a magnet link, HTTP URL, or local file. |
| pause_torrentC | Pause a torrent. |
| delete_torrent | Delete a torrent and its files. |
| forget_torrentC | Forget a torrent, keeping the files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools are clearly distinct (add, remove, start, pause, move, labels, session stats, free space). However, get_torrent_details and get_torrent_stats overlap somewhat—both retrieve information about a specific torrent—though the descriptions suggest one is more comprehensive. remove_torrent and forget_torrent are also conceptually similar but clearly differentiated by whether files are deleted.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_torrent_details, add_torrent, remove_torrent). There are no style inconsistencies or vague verbs; each name clearly indicates the action and target.
With 12 tools, the count is well within the ideal range for a torrent client MCP. Each tool addresses a legitimate operation without redundancy, covering core lifecycle actions and utility functions.
The toolset covers core lifecycle operations (add, remove, start, pause, move, set labels) and status queries, but there is no explicit tool to list all torrents. Agents must rely on get_recently_active or session statistics to infer the full set, which is a notable gap for enumeration and management workflows.