Mcp Arr
Control your self-hosted Sonarr, Radarr, Lidarr, Readarr, and Prowlarr stack from a coding agent via MCP instead of clicking each web UI.
Overview
mcp-arr is a MCP server for the Operate phase that manages Sonarr, Radarr, Lidarr, Readarr, and Prowlarr through agent tools over stdio MCP.
What is this MCP server?
- Single MCP server surface for the *arr suite: Sonarr, Radarr, Lidarr, Readarr, and Prowlarr.
- Configure each app with URL plus API key environment variables (SONARR_*, RADARR_*, LIDARR_*, READARR_*, READARR/PROWLAR
- npm package mcp-arr-server v1.0.0 with stdio transport.
- Lets agents query and manage media libraries, indexers, and related automation from one integration.
- Targets builders who already run *arr Docker or NAS stacks and want agent-driven ops.
- Integrates five *arr-family applications (Sonarr, Radarr, Lidarr, Readarr, Prowlarr)
- Published as mcp-arr-server version 1.0.0 with stdio transport
What problem does it solve?
Homelab operators waste time switching between five *arr dashboards when agents could safely call the same APIs.
Who is it for?
Indie hackers and power users running self-hosted *arr who want agent-assisted library and indexer maintenance.
Skip if: Builders with no *arr deployment, cloud-only SaaS products, or strict compliance environments that forbid media automation tooling.
What do I get? / Deliverables
After configuration, your agent can orchestrate searches, library changes, and indexer-related tasks across your *arr stack from one MCP entry.
- Unified agent tooling across up to five *arr applications
- Scriptable library and indexer operations without opening each web UI
Recommended MCP Servers
Journey fit
Media library automation is ongoing homelab and infrastructure operations after systems are deployed, not early product validation. infra fits homelab *arr orchestration, indexer sync, and library maintenance that solo operators run in production-like personal setups.
How it compares
Homelab *arr MCP bridge—not a consumer streaming app or generic Kubernetes operator.
Common Questions / FAQ
Who is mcp-arr for?
Self-hosters already running Sonarr, Radarr, Lidarr, Readarr, or Prowlarr who want MCP-driven control from a coding agent.
When should I use mcp-arr?
Use it during operate and infra work when you want agents to add series, manage indexers, or coordinate across *arr apps without manual UI steps.
How do I add mcp-arr to my agent?
Install mcp-arr-server from npm, set SONARR_URL/API_KEY and the parallel variables for each *arr instance you use, and register the stdio MCP server in your client.