Skip to main content
Glama
arr-mcps

qui-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to qui-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • qbit_manage-mcp

      arr-mcps
      A
      license
      A
      quality
      B
      maintenance
      MCP server exposing qbit_manage's Web API as tools, so an LLM can read and manage a qbit_manage instance: run maintenance commands on qBittorrent torrents, manage config files, scheduler, logs, security settings, and system state.
      6
      MIT

    • prowlarr-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Prowlarr's API v1 as tools for managing indexers, applications, download clients, and more, including cross-indexer searches and system commands.
      10
      MIT

    • rtorrent-mcp

      sandraschi
      A
      license
      B
      quality
      A
      maintenance
      MCP server for rTorrent BitTorrent automation, enabling torrent management (add/list/pause/delete), multi-source searching (Nyaa, Pirate Bay, etc.), and post-processing workflows via natural language.
      7
      1
      MIT

    • p2p-tools-mcp

      bonklek
      F
      license
      A
      quality
      B
      maintenance
      Provides MCP servers for VPN control (NordVPN) and torrent lifecycle management via Jackett search and qBittorrent operations, plus a unified CLI.
      5
      -
    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

    B3.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    The 12 tools are organized around fairly distinct functional domains (torrents, RSS, torznab, backups, etc.), so misselection is rare. The main ambiguity is `qui_system`, which acts as a catch-all for auth, licenses, arr instances, notifications, and settings, and could be confused with `qui_instances` when an agent is looking for instance management.

    Naming Consistency5/5

    All tools follow a consistent lowercase `qui_<domain>` pattern, and the underlying operations use a uniform CRUD-style naming convention such as `create_*`, `list_*`, `update_*`, and `delete_*`. There is no mixing of naming styles or unpredictable casing.

    Tool Count5/5

    Twelve tools is within the ideal 3-15 range, and each tool maps to a meaningful resource area of the qui application. Even though several tools expose a large number of sub-operations, the tool count itself is well-scoped for the server's broad purpose.

    Completeness4/5

    The surface covers CRUD and lifecycle operations across most major domains: instances, torrents, cross-seed, torznab, RSS, automations, backups, scanning, categories, and tags. A few direct actions like explicit torrent deletion are only available through generic bulk-action endpoints, but overall the coverage is strong with few dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources