Planned integration for media server management according to the README.
Planned integration for torrent download management according to the README.
Planned integration for movie management according to the README.
Provides tools for TV show management, including searching, listing, adding series, monitoring seasons, managing download queue, and viewing upcoming episodes.
๐ฌ YARR Media Stack MCP Server
A comprehensive Model Context Protocol (MCP) server that bridges the gap between Large Language Models (LLMs) and your self-hosted media technology stack. This project enables intelligent automation and natural language control of your media services while maintaining traditional programmatic access.
๐ฏ Key Features
๐ค LLM-powered natural language control of media services
๐ Modular architecture for easy service integration
๐ Unified API gateway for traditional access
๐ฎ Web UI for visual control (planned)
๐ Direct API access without LLM middleware
๐งฉ Extensible plugin system for new services
Related MCP server: OpenAPI MCP Server
๐ Documentation
๐๏ธ Project Structure
This monorepo is organized into modular packages, each serving a specific purpose:
๐ฆ
packages/server: Core MCP server implementation๐
packages/web: Web UI interface (planned)๐ฌ
packages/chatbot: LLM chat interface (planned)๐
packages/api-gateway: API routing and service coordination (planned)
๐ง Integrated Services
โ Currently Supported
Gotify - Notification Management
Sonarr - TV Show Management
Prowlarr - Indexer Management
Overseerr - Request Management
๐ง Planned Integrations
Radarr - Movie Management
qBittorrent - Torrent Management
SABnzbd - Usenet Downloads
Plex - Media Server
Tautulli - Server Statistics
TMDB - Media Database
๐ Service Documentation
๐ข Currently Integrated
๐ Planned Integration
๐งช Development
Testing Tools
๐ ๏ธ SDK References
๐๏ธ Architecture
The project follows a modular architecture where each service package contains:
๐ API client implementation
๐ Type definitions
๐ ๏ธ MCP tools for service interaction
๐ฃ๏ธ API routes
This architecture supports multiple interaction methods:
LLM-Powered Control: Natural language processing for intuitive media management
Traditional API Access: Direct API calls through the unified gateway
Web Interface: Visual control panel for service management (planned)
Chatbot Interface: Conversational UI for service control (planned)
The modular design allows for:
Easy addition of new services
Independent service deployment
Flexible interaction methods
Consistent API patterns across services
๐ Getting Started
Prerequisites
Configuration
Create
.envfile from template:
Then add your service API keys:
Configure Claude Desktop:
Important: Use full paths in your configuration to ensure Claude Desktop can find the executables and project directory.
Note: Replace
C:\\path\\to\\yarrwith your actual project directory path.