Skip to main content
Glama
rollecode

Transmission MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Transmission MCP server

No user-submitted related servers found.

    Related Servers

    • Transmission MCP Server

      cronus42
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for interacting with the Transmission BitTorrent client via natural language, enabling users to manage torrents, configure download settings, and monitor download activity.
      2
      MIT

    • Plex MCP server

      rollecode
      A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      405
      31 npm
      MIT

    • Sonarr MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Enables full control of Sonarr from Claude.ai and Claude Code by exposing all 234 v3 API operations as tools for managing media libraries.
      234
      26 npm
      MIT

    • transmission-mcp-server

      dgoo2308
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables controlling a Transmission torrent daemon, allowing adding, listing, controlling torrents and checking free space, with support for SOCKS5 proxy for remote access.
      -

    • Audiobookshelf MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Exposes all 209 Audiobookshelf API routes as tools, letting Claude.ai and Claude Code manage libraries, books, podcasts, playback, users, settings, and more.
      209
      34 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool targets a distinct resource or RPC action: torrent lifecycle, queue position, session settings, bandwidth groups, and daemon admin are cleanly separated. Close pairs like start_torrents vs start_torrents_now and set_torrent location vs move_torrent_data are explicitly differentiated in their descriptions.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern such as list_torrents, add_torrent, stop_torrents, and set_session. Minor deviations like queue_move_top/up/down/bottom and start_torrents_now break the strict pattern, though all names remain snake_case and readable.

    Tool Count3/5

    At 26 tools, the set sits just above the 16-25 'heavy' band, although nearly every tool maps to a distinct Transmission RPC operation. The four queue_move_* tools and the two start_torrents variants could be consolidated, making the count feel slightly heavy rather than egregiously bloated.

    Completeness5/5

    The surface covers the full torrent lifecycle: add, list, get, set, start, stop, verify, reannounce, remove, move, rename, and queue management. It also includes session settings, stats, bandwidth groups, free space, port testing, blocklist updates, and daemon shutdown, with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources