Skip to main content
Glama
mattmaas

qBittorrent MCP Server

by mattmaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to qBittorrent MCP Server

No user-submitted related servers found.

    Related Servers

    • qBittorrent MCP Server

      jabberjabberjabber
      F
      license
      A
      quality
      D
      maintenance
      Enables 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.
      7
      3
      -

    • qBittorrent MCP

      pickpppcc
      F
      license
      Not graded
      quality
      F
      maintenance
      A service that provides programmatic access to qBittorrent's WebUI API, enabling management of torrents, trackers, tags, speed controls, and system information through natural language.
      27
      -

    • qbittorrent-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing qBittorrent's WebUI API v2 as tools, enabling LLMs to manage torrents, categories, tags, RSS feeds, search plugins, and application settings.
      90
      2
      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.
      -

    • iptorrents MCP Server

      hubbertj
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and downloading torrents from iptorrents.com using browser cookie-based authentication, with features like filtering, sorting, and freeleech detection.
      -

    • qui-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      MCP server that exposes qui's JSON REST API as tools for monitoring and managing qBittorrent instances, torrents, automations, cross-seeding, RSS, backups, and related services.
      12
      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.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_torrent_info vs get_torrents (single vs list), pause/resume/delete are separate actions, and global settings tools are unique. No two tools could be confused for the same operation.

    Naming Consistency5/5

    All tools follow a strict qbittorrent_verb_noun pattern (e.g., get_torrent_info, add_torrent_magnet, set_speed_limits). The prefix is uniform and action verbs are consistent throughout.

    Tool Count5/5

    14 tools is well-scoped for a BitTorrent client: core torrent lifecycle (add, pause, resume, delete, recheck), querying, categories, and global settings. No tool feels redundant or missing for the stated purpose.

    Completeness4/5

    Covers torrent CRUD, state control, categories, speed limits, and app info/preferences. Minor gaps exist: no tool to add a torrent from a .torrent file (only magnet), no category creation/deletion, and no preference setting (only get). These are workaroundable but noticeable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources