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?
Allows querying media server status, recently added content, and currently playing items from a Jellyfin instance.
Enables natural language interaction with MoviePilot media library automation, supporting search, discovery, subscription management, download control, and media status queries.
10
9
MIT
Why this server?
Allows pairing zspace-cli with Jellyfin for media library tooling, such as managing files on a ZSpace NAS that can be served by Jellyfin.
CLI + SDK + MCP server for ZSpace (极空间) NAS — zero-config file management from the terminal or AI agents. No password, no SSH: reads the desktop client's login state. 12 MCP tools covering ls / find / tree / upload / download / rename / move / copy / remove.
24
612 PyPI
28
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.
16
5
MIT
Why this server?
Enables searching and playing content from Jellyfin media server on Android TV.
An MCP server that lets AI agents control Android TVs via ADB, including searching and playing content across streaming services, managing power and volume, and sending remote control commands.
6
4 npm
4
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.
10
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.
