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
      C
      quality
      B
      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.
      405
      12 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.
      234
      8 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.
      209
      58 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
      MIT

    • Jellyseerr MCP Server

      aserper
      F
      license
      Not graded
      quality
      C
      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.
      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

    B3/5.0

    Scored across 170 tools

    Disambiguation4/5

    Most tools are clearly distinguished by resource and action, and descriptions clarify the differences (e.g., settings vs. service endpoints for Radarr/Sonarr). However, some overlap exists between notification settings tools and push-subscription user tools, and between GET/PUT request updates and status-change POST endpoints, which could cause misselection.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern derived from REST paths (list_, get_, create_, update_, delete_). Even long names like create_settings_notifications_telegram_test are predictable and uniform, with no camelCase or mixed conventions.

    Tool Count2/5

    With 170 tools, the surface is severely overwhelming for an agent. Many tools could be consolidated (e.g., a single notification-settings tool with a provider parameter), and the sheer number far exceeds the typical 3-15 well-scoped range, making selection and discovery impractical.

    Completeness4/5

    The tool set covers most core CRUD and lifecycle operations for auth, users, requests, issues, media, discover, settings, and services. Minor gaps exist, such as no generic get_media_by_media_id or full update_issue (only status changes), but these are workable and the overall domain is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources