The MCP *arr Server integrates with the *arr media management suite, allowing users to manage Sonarr, Radarr, Lidarr, and Prowlarr from a single interface with natural language queries and cross-service search capabilities.
From the registry: MCP server for *arr media suite - Sonarr, Radarr, Lidarr, Readarr, Prowlarr

Please install the `mcp-arr` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **At least one *arr application** — A running instance of Sonarr, Radarr, Lidarr, or Prowlarr with API access
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","mcp-arr-server"]
- optional environment variables:
- `SONARR_URL`: Sonarr URL (example: `http://localhost:8989`)
- `SONARR_API_KEY`: Sonarr API key (example: `<your-api-key>`)
- `RADARR_URL`: Radarr URL (example: `http://localhost:7878`)
- `RADARR_API_KEY`: Radarr API key (example: `<your-api-key>`)
- `LIDARR_URL`: Lidarr URL (example: `http://localhost:8686`)
- `LIDARR_API_KEY`: Lidarr API key (example: `<your-api-key>`)
- `PROWLARR_URL`: Prowlarr URL (example: `http://localhost:9696`)
- `PROWLARR_API_KEY`: Prowlarr API key (example: `<your-api-key>`)
Note: At least one service URL+API key pair is required; configure only the services you use.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.SONARR_URLrequiredURL for the Sonarr applicationSONARR_API_KEYrequiredAPI key for the Sonarr applicationRADARR_URLrequiredURL for the Radarr applicationRADARR_API_KEYrequiredAPI key for the Radarr applicationLIDARR_URLrequiredURL for the Lidarr applicationLIDARR_API_KEYrequiredAPI key for the Lidarr applicationPROWLARR_URLrequiredURL for the Prowlarr applicationPROWLARR_API_KEYrequiredAPI key for the Prowlarr application