Transmission MCP server
Related Servers
Alternatives to Transmission MCP server
No user-submitted related servers found.
Related 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.2MIT
- AlicenseBqualityAmaintenanceEnables running Plex from Claude.ai and Claude Code by exposing all 405 operations as tools, covering both your media server and plex.tv cloud services with automatic routing to the appropriate host.2826 npmMIT
- AlicenseCqualityAmaintenanceEnables full control of Sonarr from Claude.ai and Claude Code by exposing all 234 v3 API operations as tools for managing media libraries.23510 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables controlling a Transmission torrent daemon, allowing adding, listing, controlling torrents and checking free space, with support for SOCKS5 proxy for remote access.-
- AlicenseCqualityAmaintenanceExposes all 209 Audiobookshelf API routes as tools, letting Claude.ai and Claude Code manage libraries, books, podcasts, playback, users, settings, and more.21272 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables voice assistants to start, monitor, message, and approve local Claude Code sessions on your computer, including sessions already open in a terminal. It exposes session management, recaps, approvals, and history search as MCP tools.1GPL 3.0
TDQS
Scored across 27 tools
Almost every tool targets a distinct resource+action, and descriptions are unusually thorough about differences (e.g. set_torrent's location vs move_torrent_data, start_torrents vs start_torrents_now). The only mild confusions are the start_torrents/start_torrents_now pair and set_torrent overlapping move/queue operations, but documentation resolves them.
All names use a consistent snake_case verb_noun pattern (get_session, set_torrent, list_torrents, add_torrent, remove_torrent, move_torrent_data). Variants like queue_move_top and start_torrents_now stay within the same convention and remain readable.
27 tools is heavy for a single daemon client and exceeds the comfortable range. Some could consolidate (e.g. the four queue_move_* tools into one parameterized tool), though each tool does map to a real, distinct RPC capability.
The surface covers the full torrent lifecycle (add/get/list/remove/set/move/rename/verify), queue control, bandwidth groups, session settings, blocklist, port test, free space, and even result paging. No obvious gaps or dead ends for the stated purpose.