Skip to main content
Glama
rollecode

seerr-mcp

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to seerr-mcp

No user-submitted related servers found.

    Related Servers

    • Plex MCP server

      rollecode
      A
      license
      B
      quality
      A
      maintenance
      Enables running Plex from Claude.ai and Claude Code by exposing all 405 operations as tools, covering both your media server and plex.tv cloud services with automatic routing to the appropriate host.
      28
      31 npm
      MIT

    • 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
      30 npm
      MIT

    • Audiobookshelf MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Exposes all 209 Audiobookshelf API routes as tools, letting Claude.ai and Claude Code manage libraries, books, podcasts, playback, users, settings, and more.
      212
      78 npm
      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
      1
      MIT

    • Jellyseerr MCP Server

      aserper
      F
      license
      A
      quality
      B
      maintenance
      Enables interaction with Jellyseerr media request systems through natural language. Supports searching for media, creating requests, checking request status, and managing your media library workflow.
      5
      8
      -
    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 171 tools

    Disambiguation2/5

    With 171 tools covering the entire Overseerr/Jellyseerr API, there are many near-duplicates and overlapping surfaces. For instance, list_settings_radarr vs list_service_radarr, get_movie_by_movie_id_ratings vs get_movie_by_movie_id_ratingscombined, and several get_/list_ pairs with subtly different endpoints create significant ambiguity. The sheer volume and similar naming patterns make it easy for an agent to pick the wrong tool.

    Naming Consistency3/5

    The names largely follow a verb_noun_by_id pattern, but the verb choice is inconsistent and often misleading (e.g., create_ for POST status updates, list_ for GET operations that aren't lists). The API-derived naming with by_id suffixes is systematic but not semantically clean, and some names like list_search are awkward.

    Tool Count1/5

    171 tools is an extreme mismatch for a usable MCP server. Even a comprehensive API surface should be curated or bundled; exposing every endpoint individually overwhelms an agent's context and decision-making. This is a clear case of excessive tool count.

    Completeness4/5

    The surface appears to cover the full Overseerr API comprehensively, including CRUD for users, requests, issues, settings, discovery, and services. Only minor gaps (e.g., some niche notification or status endpoints) might exist, but overall it's very complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources