Yarr MCP

Rust MCP and CLI server for Sonarr, Radarr, Prowlarr, Plex, Jellyfin, and download clients.

Yarr MCP is a Rust-implemented MCP server and CLI tool that bridges AI agents to a suite of self-hosted media management applications. It targets the core components of a typical home or private media stack: Sonarr for TV series management, Radarr for movie management, Prowlarr as an indexer aggregator, Plex and Jellyfin as media servers, and associated download clients. Configuration is handled entirely through environment variables. Connections to Sonarr and Radarr require their respective base URLs and API keys via YARR_SONARR_URL, YARR_SONARR_API_KEY, YARR_RADARR_URL, and YARR_RADARR_API_KEY. Plex connectivity requires YARR_PLEX_URL and YARR_PLEX_TOKEN. Additional variables control versioning, repository location, release base URL, and Rust logging verbosity. The server communicates over stdio transport, meaning it must be launched as a subprocess by the MCP host rather than accessed over a network socket. It is published on npm under the identifier yarr-mcp at version 1.1.1. No tools are currently enumerated in the registry record, so the specific agent-callable actions are not documented here. This server is the right fit when an agent needs to interact programmatically with an existing self-hosted Sonarr, Radarr, Plex, or Jellyfin installation.

Use cases

  • Automate queries or updates to a Sonarr TV library from an AI agent
  • Manage Radarr movie collections through an agent workflow
  • Integrate Prowlarr indexer operations into an automated media pipeline
  • Allow an agent to interact with a Plex or Jellyfin media server
  • Connect download client management to an AI-driven orchestration layer

When to use it

  • The agent needs to interact with a self-hosted Sonarr, Radarr, Plex, or Jellyfin instance
  • The MCP host supports stdio transport for subprocess-based servers
  • All required service URLs and API keys are available as environment variables
  • A Rust-based server binary is acceptable in the deployment environment

When not to use it

  • No self-hosted Sonarr, Radarr, Plex, or Jellyfin instances are available
  • The MCP host requires HTTP/SSE transport rather than stdio
  • Specific tool-level capabilities need to be verified before adoption — the registry record lists no tools
  • A fully managed or cloud-hosted media service is in use instead of self-hosted software