Skip to main content
Glama

Related Servers

Alternatives to Plex MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage and control their Plex media library through natural language commands in MCP-compatible AI clients. It supports searching content, managing playlists, tracking library statistics, and monitoring live viewing sessions.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server for Plex Media Server that enables natural language interaction with your media library, including search, browse, and chat features via an optional web app.
      22
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that gives AI assistants access to your self-hosted Audiobookshelf library, enabling queries about current listening, searching, and browsing.
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to query Prometheus metrics, discover available data, and analyze system performance through natural language interactions.
      5
      309 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 54 tools

    Disambiguation4/5

    Domain prefixes (sonarr_, radarr_, trakt_) cleanly separate the three integrations, and Plex tools mostly target distinct resources (libraries, playlists, sessions, stats). The main soft spot is the analytics cluster — get_watch_stats, get_user_stats, get_library_stats, get_popular_content, and get_fully_watched vs get_watch_history vs get_recently_watched overlap enough that an agent could pick the wrong one for a 'what have I watched' question.

    Naming Consistency4/5

    Nearly everything follows a predictable prefix_verb_noun snake_case pattern (get_library_items, sonarr_add_series, radarr_create_tag), making the surface readable and scannable. Minor deviations like trakt_sync_from_trakt (redundant domain word), search_media, and export_library slightly break the verb-first convention but don't cause confusion.

    Tool Count2/5

    At 54 tools this is well past a comfortable surface for an agent to select from reliably, and much of the bulk is duplicated structure between Sonarr and Radarr (get_movies/series, search, add, missing, queue, calendar, profiles, trigger_search, four tag tools). The multi-integration scope partly justifies the size, but many near-parallel tools could be consolidated or parameterized.

    Completeness3/5

    Read/analytics coverage is extensive and the Sonarr/Radarr tag lifecycle is fully CRUD, but there are notable dead ends: get_editable_fields exists with no corresponding update/edit media tool, playlists can be read but not created or modified, and watchlist/watch-history are read-only. Sonarr/Radarr also lack delete/edit for series and movies, so routine maintenance operations are unreachable.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data