Oraclarr MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      - /var/run/docker.sock:/var/run/docker.sock:ro

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add oraclarr -- uvx oraclarr-mcp

{
  "mcpServers": {
    "oraclarr": {
      "command": "uvx",
      "args": [
        "oraclarr-mcp"
      ]
    }
  }
}

[mcp_servers.oraclarr]
command = "uvx"
args = ["oraclarr-mcp"]

{
  "mcpServers": {
    "oraclarr": {
      "command": "uvx",
      "args": [
        "oraclarr-mcp"
      ]
    }
  }
}

{
  "servers": {
    "oraclarr": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "oraclarr-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: ORACLARR_SONARR_URL (Sonarr base URL, e.g. http://192.168.1.10:8989. Every service is ORACLARR_<NAME>_URL plus ORACLARR_<NAME>_API_KEY; the README lists the types), ORACLARR_SONARR_API_KEY (Sonarr API key (Settings > General)), ORACLARR_RADARR_URL (Radarr base URL, e.g. http://192.168.1.10:7878), ORACLARR_RADARR_API_KEY (Radarr API key (Settings > General)), ORACLARR_CONFIG (Optional path to a config.yaml as an alternative to ORACLARR_* variables. See docs/config-file.md in the repository).