Yarr MCP server

yarr

Self-hosted media fleet operations across Sonarr, Radarr, Plex, and related apps over MCP and CLI.

If you run Claude Code, Codex, or Gemini CLI against a self-hosted media stack, yarr gives an agent one consistent way to query and control all of it instead of eleven different ad hoc integrations. It is an upstream-client MCP server: it does not replace those applications or mirror every REST endpoint as a web UI. Its job is to provide one consistent tool surface for agents and one equivalent CLI surface for operators.

Not for: a general-purpose REST gateway to arbitrary services, or a scheduler/automation engine in its own right. yarr only talks to the service kinds it knows about, and only does what you or your agent ask it to do.

Contents

• Naming
• Capabilities And Boundaries
• Install
• Unraid Plugin
• Quickstart
• Client Configuration
• Runtime Surfaces
• MCP Tool Reference
• CLI Reference
• Configuration
• Authentication
• Safety And Trust Model

Naming

This repository is published at github.com/dinglebear-ai/yarr.

The Rust package and installed binary are both yarr. The npm launcher package is yarr-mcp because the shorter yarr name is occupied on npm; installing the launcher still gives you a yarr command. The MCP registry name is ai.dinglebear/yarr, and Docker images use ghcr.io/dinglebear-ai/yarr. Production Compose deployments select that image by immutable manifest digest.

Plugin naming is intentionally split:

@dinglebear/yarr npm package over stdio and includes every per-service fallback skill; it does not commit a platform-specific binary.

• yarr is the full MCP server plugin. It launches the repository-coupled

jellyfin, tautulli, tracearr, and bazarr are skills-only plugins with no MCP server and no bundled binary.

• sonarr, radarr, prowlarr, overseerr, sabnzbd, qbittorrent, plex,

Capabilities And Boundaries

yarr wraps a configured media automation fleet through one action-dispatched service layer. The same implementation backs MCP and CLI calls, so behavior does not drift between "agent used the tool" and "operator ran the command."

Primary capabilities:

Overseerr, Jellyfin, and Plex. The executor preserves the declared parameter, request-media, and successful-response transport contract; unsupported rows are excluded and listed in the generated capability matrix.

• Fleet status checks across the configured services.
• Credentialed upstream API passthrough for known service kinds.
• Table-driven OpenAPI operation metadata for Sonarr, Radarr, Prowlarr,

whose upstreams do not ship usable machine-readable specs.

• Curated commands for SABnzbd, qBittorrent, Tautulli, Bazarr, and Tracearr,

• Code Mode over MCP for multi-step media automation scripts.
• Snippet storage and execution for repeatable Code Mode workflows.
• Skills-only direct-HTTP plugin fallbacks for each individual service.

Boundaries:

arguments. Credentials come from environment variables, config files, or strict per-service plugin config JSON.

• yarr does not store or schedule media jobs on its own.
• It does not expose a local REST action API or embedded web UI.
• It does not accept arbitrary unknown service kinds.
• MCP callers never provide credentials, tokens, keys, or secrets as action

Shortened. The full README is on GitHub.