Skip to main content
Glama
arr-mcps

radarr-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to radarr-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-arrstack

      indlns
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.
      MIT

    • arr-stack-mcp

      new-usemame
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that exposes Sonarr, Radarr, Lidarr, and Jellyfin to any MCP client through a curated tool layer for LLM consumption.
      MIT

    • lidarr-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Lidarr's full v1 REST API as tools for reading and managing artists, albums, tracks, queue, history, and more. It enables LLMs to interact with a Lidarr instance via natural language.
      15
      MIT

    • radarr-mcp-server

      Barrow1990
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect to a Radarr instance over HTTP to manage and query movies, including listing, searching, triggering downloads, and checking system status.
      MIT
    • profilarr-mcp by arr-mcps

      profilarr-mcpofficial

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Profilarr's v1 REST API as tools, enabling an LLM to inspect and manage linked databases, connected Radarr/Sonarr instances, backups, jobs, announcements, and system status.
      20
      MIT

    • seerr-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      MCP server exposing Seerr's full v1 REST API as tools, enabling LLMs to search and discover media, manage requests and approvals, users, issues, watchlists, and integration settings for Plex/Jellyfin/Emby and Sonarr/Radarr, including reads and writes with destructive operations flagged.
      15
      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 226 tools

    Disambiguation3/5

    Many tools follow a clear resource+action pattern, but there are several ambiguous groups (e.g., radarr_list_queue vs radarr_get_queue_details vs radarr_get_queue_status, and radarr_bulk_edit_moviefiles vs radarr_bulk_update_moviefile). The sheer number of similar resource-specific list/get tools for different contexts (movies, history, blocklist, importlist) could cause misselection.

    Naming Consistency3/5

    The dominant pattern is radarr_<verb>_<resource>, but there are deviations: 'action' is a vague verb, 'test_all' is inconsistent with plain 'test', and resource naming varies ('importlist' vs 'import_list', 'moviefile' vs 'moviefiles'). While readable, the inconsistencies could be more standardized.

    Tool Count1/5

    With 226 tools, this server is massively over-scoped. Even a complex application like Radarr does not need this many discrete operations. The tool count drowns an agent in choices and is far beyond the typical 3-15 well-scoped range.

    Completeness5/5

    The tool surface is exhaustively complete, covering full CRUD/lifecycle for all major resources (movies, quality profiles, download clients, indexers, notifications, etc.) plus auxiliary operations like backup, system, and command execution. There are no obvious gaps for the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources