Skip to main content
Glama
HoneyBearTech

plex-director-mcp

by HoneyBearTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to plex-director-mcp

No user-submitted related servers found.

    Related Servers

    • Plex-MCP

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

    • mcp-it-ops

      bastiaan365
      F
      license
      A
      quality
      D
      maintenance
      Exposes homelab and IT-ops tools to Claude, including system health monitoring, Grafana alert states, Docker container status, Loki logs, SMART disk health, and more.
      8
      1
      -

    • plex-mcp-server

      aminamos
      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.
      68 npm
      MIT

    • 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
      19 npm
      MIT
    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.7/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools have distinct resource/action pairings, but get_cluster_hardware_analytics and get_cluster_infrastructure_health overlap heavily on CPU/RAM reporting, and the two search tools require careful reading to distinguish local Plex search from TMDb selection. Descriptions largely clarify the boundaries, so the issue is present but not severe.

    Naming Consistency5/5

    All tool names follow a clean snake_case verb_first pattern, with information retrieval consistently using get/check and actions using purpose-specific verbs like manage, resolve, confirm, and plan. There is no mixing of casing styles or chaotic verb usage.

    Tool Count3/5

    At 17 tools, the set sits in the borderline heavy range, though the breadth of subsystems covered—Plex, Tautulli, Radarr, Prowlarr, qBittorrent, and cluster infrastructure—partly justifies the count. Several overlapping health/analytics tools could be consolidated to make the surface feel tighter.

    Completeness4/5

    The core movie workflow is well covered: discover candidates via TMDb, confirm them into Radarr, check their status, diagnose missing media, and plan upgrades. Minor gaps exist, such as no direct remove/delete flow and no Sonarr/TV management, but they do not break the apparent movie-centric scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources