MCP server exposing Dashbrr's REST API as tools, so an LLM can read and manage a dashbrr instance: configured services, per-service health, and summary panels for many apps. Write tools cover settings management, download-queue deletes, Overseerr approvals, UI preferences, and the Plex auth PIN flow.
34
MIT
Why this server?
Saves downloaded catchup programmes with Jellyfin-compatible naming (e.g. 'Show/Season 02/Show - S02E05 - Title.mkv' or air-date naming) and writes matching .nfo metadata files, so recordings drop straight into a Jellyfin library.
Enables AI assistants to search an Xtream Codes IPTV provider's TV guide, past and upcoming, and download catchup programmes in the background, naming them for Jellyfin or Plex libraries. Also handles subscription status, download tracking and finish notifications.
12
MIT
Why this server?
Provides tools for querying Jellyfin monitoring data through Tracearr, including watch history, active streams, media, users, libraries, and recently added items.
MCP server exposing Tracearr's Public API v2 as read-only tools to query Plex, Jellyfin, and Emby monitoring data such as watch history, active streams, media, users, libraries, and recently added items.
13
MIT
Why this server?
Provides tools for interacting with Jellyfin to check service health and version, see who is currently watching, and make other API calls such as refreshing libraries.
Enables Claude to monitor and manage a self-hosted media stack—including Sonarr, Radarr, Prowlarr, Bazarr, Overseerr, qBittorrent, and Jellyfin—through tools for status, queues, searches, additions, requests, downloads, and now-playing checks. It also supports arbitrary API calls with safety levels and secret redaction.
13
MIT
Why this server?
Provides automated deployment and management of Jellyfin media server through service templates.
Enables AI assistants to manage homelab infrastructure through automated service installation (Jellyfin, Pi-hole, Ollama, Home Assistant, Frigate NVR), VM operations, AI accelerator support (MemryX, Coral TPU, Hailo-8), and Terraform state management with SSH-based discovery and deployment.
58
5
MIT
Why this server?
Manages Jellyfin integration settings, including library configuration, user sync, and quick connect authentication in a Seerr instance.
MCP server exposing Seerr's full v1 REST API as tools, enabling LLMs to search and discover media, manage requests and approvals, users, issues, watchlists, and integration settings for Plex/Jellyfin/Emby and Sonarr/Radarr, including reads and writes with destructive operations flagged.
15
1
MIT
Why this server?
Provides tools for interacting with Jellyfin media server, including checking status, adding library paths, creating libraries, scanning libraries, and running tasks.
Enables an agent to oversee and operate a fleet of Linux servers over the system ssh and Tailscale — inspecting host status, auditing configuration, tracking drift and reading history across many machines. Every mutating operation runs as a dry-run plan first and only applies after explicit confirmation of that exact plan, rolling out one host at a time with a local journal.
63
MIT
Why this server?
Provides tools for interacting with a Jellyfin media server, enabling agents to search the library, retrieve item metadata, list active playback sessions, view media libraries, and fetch next-up episodes.
Enables AI agents to interact with a Jellyfin media server, allowing them to search the library, fetch item details, list active playback sessions, and retrieve next-up episodes.
5
MIT
Why this server?
Provides reference guidance for integrating Lampa with Jellyfin's content API, helping plugin authors use Jellyfin as a third-party content provider.
MCP server for AI-assisted development on the Lampa open-source TV app, providing read-only access to the source tree with 41 tools and 5 resources for structured analysis, planning, editing, and validation.
