mcp-arr

The MCP arr server provides a unified interface to manage and query your *arr ecosystem (Sonarr, Radarr, Lidarr, and Prowlarr) from a single chatty or natural language-enabled interface. It exposes tools to check connection status, search across all configured services, as well as per-service capabilities like listing libraries, triggering downloads, and inspecting queues or calendars. Use natural language prompts to perform cross-service lookups, or target a specific service to retrieve or manipulate content across your media stack. The included tools let you enumerate series, movies, or artists, initiate or monitor downloads, view calendars, and test health across indexers and services.

Available general tools include arr_status (check connections) and arr_search_all (cross-service search). Specific service tools cover Sonarr (tv) operations such as listing series, searching, adding series, accessing quality profiles, and viewing the download queue or calendar; Radarr (movies) with similar capabilities for films; Lidarr (music) for artists and albums; and Prowlarr (indexers) for managing indexers, health, and statistics. The server also supports configuration review and cross-service status checks, enabling unified management of your entire *arr ecosystem from one place.

Prerequisites

• Node.js 18+ installed on the host
• Access to at least one running *arr application (Sonarr, Radarr, Lidarr, Prowlarr) with API access
• Git and npm (npm is installed with Node.js)

Option A: Install and run via npm (recommended)

1. Ensure Node.js 18+ is installed
2. Run the MCP server directly using npx (as designed by the project):

npx mcp-arr-server

Option B: Install from source

1. Clone the repository

git clone https://github.com/aplaceforallmystuff/mcp-arr.git
cd mcp-arr

2. Install dependencies

npm install

3. Build the project (if the repository requires a build step)

npm run build

4. Start the server (depending on how the package exposes it; typically via npm start or node dist/server.js)

Notes
- The README indicates the server is designed to run via npx (mcp-arr-server). If you prefer a local install, ensure package.json provides an executable script for start/build.
- Ensure your environment variables are set to point to your running *arr services (Sonarr, Radarr, Lidarr, Prowlarr) and include the necessary API keys as described in the configuration section.

Environment variables determine which services are detected. Only configure the services you actually have running. If certain keys are missing, the server will skip those services. When using Claude Desktop/Code integrations, you can embed the mcpServers configuration in the respective config files (arr example shown in the README). Typical configuration includes: SONARR_URL, SONARR_API_KEY, RADARR_URL, RADARR_API_KEY, LIDARR_URL, LIDARR_API_KEY, PROWLARR_URL, PROWLARR_API_KEY. If you encounter connectivity issues, verify network access to each *arr application, ensure the API keys are correct, and confirm that the applications’ API ports are reachable from the MCP server host. For cross-service searches, the server will aggregate results across connected services and present unified results.