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.
      235
      10 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

    • prowlarr-mcp-server

      Barrow1990
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients to Prowlarr over HTTP, enabling management of indexers, release searches, and system status checks through natural language tools.
      MIT

    • seerr-mcp

      rollecode
      A
      license
      C
      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.
      171
      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.
      90
      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

    C2.6/5.0

    Scored across 129 tools

    Disambiguation3/5

    Most tools target distinct resources with clear action prefixes, but many share near-identical patterns (e.g., create_indexer_test, create_indexer_testall, create_indexer_action_by_name) and generic verbs like 'Create' don't distinguish actions well. Some overlap between get_by_id_api and get_indexer_by_id_newznab, and between bulk vs single operations may cause confusion.

    Naming Consistency4/5

    Tool names consistently follow a verb_noun pattern with snake_case throughout, which is predictable. Minor inconsistencies exist (e.g., get_by_path vs get_content_by_path, list_root vs get_result_page), but the majority are well-structured.

    Tool Count1/5

    129 tools is far too many for an MCP server; this is a nearly complete REST API surface with excessive granularity. Many tools are redundant variants (e.g., test, testall, action_by_name for each resource) that likely overwhelm an agent's selection process.

    Completeness4/5

    The toolset covers a comprehensive range of operations for Prowlarr (CRUD for indexers, applications, download clients, notifications, tags, config, system, search, etc.). Minor gaps like indexer status update or tag detail mutation are not critical for most workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources