Skip to main content
Glama
rollecode

Prowlarr MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Prowlarr MCP server

No user-submitted related servers found.

    Related Servers

    • 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
      8 npm
      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

    • seerr-mcp

      rollecode
      A
      license
      B
      quality
      A
      maintenance
      Enables running Overseerr or Jellyseerr from Claude.ai and Claude Code, with all 170 API operations exposed as tools for managing requests, settings, users, issues, and media services.
      170
      MIT

    • sonarr-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      Exposes the Sonarr v3 REST API as MCP tools, enabling LLMs to read and manage a Sonarr instance including series, episodes, downloads, history, and more. Supports both read and write operations, with destructive tools flagged.
      15
      MIT

    • Bazarr MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Enables management of Bazarr subtitles through all 89 API operations, including blacklists, wanted lists, provider configuration, language profiles, and Plex/Jellyfin integrations.
      89
      MIT

    • prowlarr-mcp

      amphineko
      F
      license
      A
      quality
      B
      maintenance
      Enables searching and retrieving release metadata from Prowlarr indexers, with configurable query types, indexer and category filters, result limits, and offsets for use in automated workflows.
      1
      -
    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

    C2.4/5.0

    Scored across 128 tools

    Disambiguation2/5

    Multiple tools share identical or near-identical descriptions, such as the two "Read Newznab" tools (get_by_id_api and get_indexer_by_id_newznab) and the many generic "Create X" variants (create_indexer, create_indexer_test, create_indexer_testall). Static resource tools (get_by_path, get_content_by_path, list_root, list_login) also blur together. An agent would struggle to reliably pick the correct tool without deeper inspection.

    Naming Consistency3/5

    The dominant pattern is verb_noun (create_indexer, list_indexer, update_indexer, delete_indexer), but there are notable exceptions like get_by_id_api, get_by_path, and get_indexer_by_id_newznab that break the convention. Plural/singular mixing (applications vs appprofile) and inconsistent action naming (test vs testall vs action_by_name) further reduce consistency, though the general style remains readable.

    Tool Count1/5

    With 128 tools, this server exposes the entire Prowlarr API surface with little curation. This is far beyond the typical well-scoped MCP server range and creates a heavy, intimidating surface for agents. The count represents an extreme mismatch for a focused tool set.

    Completeness4/5

    The tool set provides extensive CRUD coverage across major resources: applications, indexers, download clients, notifications, tags, config, and more. Operations like search, history, health, logs, and system tasks round out the surface. Minor gaps exist (e.g., no explicit create backup or update command), but overall the domain is very thoroughly covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources