Plex MCP Server
Related Servers
Alternatives to Plex MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseAqualityAmaintenanceAn 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.222MIT
- AlicenseNot gradedqualityBmaintenanceA comprehensive Model Context Protocol server that bridges LLMs with self-hosted media services, enabling natural language control of TV shows, movies, downloads, and notifications while maintaining traditional API access.12AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that gives AI assistants access to your self-hosted Audiobookshelf library, enabling queries about current listening, searching, and browsing.1MIT
- FlicenseNot gradedqualityFmaintenanceA Python-based Model Context Protocol server that allows AI assistants like Claude to access and query your movie and TV show collection via Radarr and Sonarr APIs.47-
- AlicenseBqualityFmaintenanceA Model Context Protocol server that enables AI assistants to query Prometheus metrics, discover available data, and analyze system performance through natural language interactions.5103 npmMIT
TDQS
Scored across 58 tools
The tools are grouped by domain (Plex, Trakt, Sonarr, Radarr) with distinct prefixes, making most tools clearly distinguishable. However, there are some overlapping concepts within Plex stats (e.g., get_watch_history vs get_watch_stats vs get_user_stats vs get_library_stats) and update_metadata vs update_metadata_from_json, which could cause minor confusion in tool selection.
The naming pattern is mostly consistent, using verb_noun structure with domain prefixes (get_, update_, create_, etc., for Plex; trakt_*, sonarr_*, radarr_* for integrations). Minor deviations exist, such as arr_get_status instead of a per-integration prefix, and some tools like update_metadata_from_json are verbose but still follow the pattern.
With 58 tools, this server is quite heavy. While the integrations with Trakt, Sonarr, and Radarr expand the scope, the sheer number makes it overwhelming for an agent to parse and select the right tool, especially with many similar get_* functions. This exceeds the typical comfortable range and borders on being excessive for a single MCP server.
The tool surface covers the core workflows for Plex (browsing, metadata, playlists, watchlist, ratings, watch status) and integrations with Trakt (auth, sync, scrobbling) and Sonarr/Radarr (adding, searching, monitoring). Minor gaps exist, such as absence of update/delete operations for Sonarr/Radarr and no media deletion from Plex, but these are not critical for typical usage.