Skip to main content
Glama

Related Servers

Alternatives to seerr-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      MCP server for Overseerr media request management. Enables AI assistants to search for media, view requests, and manage media requests through the Model Context Protocol.
      12
      -
    • A
      license
      C
      quality
      A
      maintenance
      MCP server exposing Radarr's v3 REST API as tools, enabling LLMs to read and manage movies, downloads, history, indexers, and more.
      100
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      MCP server that exposes the Bookshelf (Readarr fork) v1 REST API as tools, allowing an LLM to read and manage authors, books, book files, editions, series, download queue, history, indexers, import lists, custom formats, tags, commands, and system status, with full read/write access and destructive tools flagged.
      15
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Overseerr that enables searching, requesting, and managing media (movies and TV shows) through natural language, with integration to Radarr/Sonarr for automated downloads.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for managing a media server stack (Plex, Radarr, Overseerr, Bazarr, Prowlarr, Trakt.tv) using natural language to browse, request, and discover content.
      12
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language discovery and resolution of movies and TV shows into verified canonical media, then requesting them through an existing Seerr/Radarr/Sonarr stack. Exposes these capabilities via MCP tools and a REST API for AI agents.
      MIT

    TDQS

    B3.3/5.0

    Scored across 15 tools

    Disambiguation2/5

    Many tools have overlapping purposes and similar names, e.g., `seerr_create_settings_jellyfin` updates settings while `seerr_create_settings_radarr` creates an instance, and there are numerous `seerr_list_settings_*` and `seerr_update_settings_*` tools with subtle differences. The inconsistent use of 'create' for both create and update operations creates ambiguity.

    Naming Consistency2/5

    The naming convention is inconsistent: some tools use `list_`, some use `get_`, some use `create_` for updates, and there are oddities like `seerr_get_issuecomment` vs `seerr_get_issue`. CamelCase is used in some sub-parts, and singular/plural is mixed (e.g., `seerr_list_user` vs `seerr_list_issue`).

    Tool Count1/5

    The server exposes an extremely large number of tools (well over 100), far exceeding the stated count of 15. This makes the tool set unwieldy and difficult for an agent to navigate efficiently.

    Completeness5/5

    The tool set covers the major domains of a media management system: settings, users, discover, media titles, auth, issues, search, requests, blocklist, watchlist, and system status. CRUD operations are available for most resources, and there are no obvious missing operations that would hinder core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues