Skip to main content
Glama

Related Servers

Alternatives to Plex MCP server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables full management of a Plex Media Server via Claude, including browsing libraries, fixing metadata, managing collections, and more.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes every documented Plex Media Server API operation as a callable tool, plus curated tools for library browsing, media search and editing, playlists, collections, live sessions, user analytics, recommendations, watchlists, playback control and subtitles. Enables clients to query, automate and control a Plex server, discover owned servers and control playback clients through natural language.
      110 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables running Overseerr or Jellyseerr from Claude.ai and Claude Code, with all 170 API operations exposed as tools for managing requests, settings, users, issues, and media services.
      170
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI assistants browse your libraries, search media, get viewing recommendations, check what's on deck, and more — all read-only against your local Plex instance.
      110 npm
      1
      MIT
    • 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
    • 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

    TDQS

    C2.2/5.0

    Scored across 405 tools

    Disambiguation1/5

    With 405 auto-generated tools, many are near-duplicates or have unclear boundaries, such as delete_playlists vs delete_playlists_by_playlist_id and multiple library section listing variants. Several GET tools are even described as 'Set...' while POST/PUT versions of the same path exist, making misselection very likely.

    Naming Consistency2/5

    Names follow a raw HTTP-verb-plus-path pattern (create_/get_/list_/update_/delete_), but 'get' and 'list' are used inconsistently for GET endpoints, and 'create_' is applied to non-creation actions like create_timeline and create_status_sessions_terminate. Oddities like list_resources_2 and list_prefs_get further break predictability.

    Tool Count1/5

    405 tools is an extreme count for a single MCP server and appears to be an uncurated dump of the entire Plex REST API. This overwhelms context and makes tool selection impractical; a much smaller curated subset would be appropriate.

    Completeness4/5

    The surface is exhaustive, covering library, playlists, play queues, sessions, DVR, sync, users, and system settings, so few major operations are missing. It loses a point because the raw endpoint dump includes many low-level/legacy operations and uneven lifecycle pairs rather than a clean, coherent API surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues