Skip to content
Grok

Yarr MCP for Grok

ai.dinglebear/yarr

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

client:Grok transport:stdio runtime:npm

Install Yarr MCP in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "yarr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dinglebear/yarr"
      ],
      "env": {
        "YARR_SONARR_URL": "<YARR_SONARR_URL>",
        "YARR_SONARR_API_KEY": "<YARR_SONARR_API_KEY>",
        "YARR_RADARR_URL": "<YARR_RADARR_URL>",
        "YARR_RADARR_API_KEY": "<YARR_RADARR_API_KEY>",
        "YARR_PLEX_URL": "<YARR_PLEX_URL>",
        "YARR_PLEX_TOKEN": "<YARR_PLEX_TOKEN>",
        "YARR_VERSION": "<YARR_VERSION>",
        "YARR_REPO": "<YARR_REPO>",
        "YARR_RELEASE_BASE_URL": "<YARR_RELEASE_BASE_URL>",
        "RUST_LOG": "<RUST_LOG>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Yarr MCP in other clients