Arr-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIDARR_URL | No | URL of the Lidarr instance | |
| RADARR_URL | No | URL of the Radarr instance | |
| SONARR_URL | No | URL of the Sonarr instance | |
| READARR_URL | No | URL of the Readarr instance | |
| PROWLARR_URL | No | URL of the Prowlarr instance | |
| LIDARR_API_KEY | No | API key for Lidarr | |
| RADARR_API_KEY | No | API key for Radarr | |
| SONARR_API_KEY | No | API key for Sonarr | |
| READARR_API_KEY | No | API key for Readarr | |
| PROWLARR_API_KEY | No | API key for Prowlarr |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| arr_get_servicesA | List which *ARR services are configured and available |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools.
The single tool name follows a clear snake_case verb_noun pattern, which is consistent.
One tool is too few for a server that presumably manages *ARR services, which typically require multiple operations.
The tool only lists services, missing essential actions like adding, updating, or deleting services, leaving significant gaps.