Skip to main content
Glama
sandraschi

PlexMCP

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to PlexMCP

No user-submitted related servers found.

    Related Servers

    • nas-mcp-server

      matthieurosset
      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

    • Plex MCP Server

      niavasha
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI assistants to query and manage Plex Media Server content through natural language, providing library access, viewing statistics, and media management capabilities.
      58
      68 npm
      50
      JavaScript
      MIT

    • Plex Assistant MCP

      axelterrier
      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

    • overseerr-mcp

      Milli42
      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.
      -
    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

    A3.5/5.0

    Scored across 22 tools

    Disambiguation2/5

    Many tools have overlapping operational boundaries, such as plex_media, plex_metadata, and plex_library all handling metadata updates, plex_search overlapping with plex_media's search functionality, and plex_performance/plex_quality both managing quality profiles. The portmanteau pattern provides some structure but does not fully resolve which tool an agent should select for a given task.

    Naming Consistency4/5

    The vast majority of tools follow the plex_<domain> pattern, and even descriptive names like plex_media_enrichment and plex_natural_assistant are readable. However, arr_stack and agentic_plex_workflow break the prefix pattern, and the use of 'mgr' in plex_ffmpeg_mgr and plex_audio_mgr introduces a slight inconsistency. Overall, the naming is predictable and easy to navigate.

    Tool Count3/5

    22 tools is on the high end of the typical range, but the portmanteau design consolidates dozens of operations into manageable groups. The count feels inflated because many tools cover closely related domains (e.g., four tools touching metadata), but the server's broad scope justifies the number. It is borderline heavy but not excessive.

    Completeness5/5

    The server covers an exceptionally broad range of Plex functionality: library CRUD, metadata management, search, playlists, streaming, users, performance, quality, reporting, RAG, integrations, FFmpeg repair, and multi-step workflows. There are no obvious dead ends or missing operations for a Plex-oriented MCP server.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources