MCP Radarr And Sonarr Server MCP Server

MCP Server for Radarr and Sonarr services. The mcp radarr and sonarr server mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

An MCP server that integrates with Radarr and Sonarr to manage your media library.

• Browse your movie and TV show library
• Search and filter media by year and genre
• Request downloads for movies and TV shows
• Check download and monitoring status
• System health monitoring and management
• Disk space monitoring

Its toolset

Everything the assistant can do here goes through one of these:

• search_media — Search for movies or TV shows with filters: typescript { mediaType: "movie" | "series", // Required year?: number, // Optional genre?: string //
• request_download — Request a download for specific media: typescript { mediaType: "movie" | "series", // Required id: number // Required }
• check_status — Check the status of specific media: typescript { mediaType: "movie" | "series", // Required id: number // Required }
• get_system_status — Get system health and storage information: typescript { system: "radarr" | "sonarr" | "both" // Required - Which system to check }

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 4 environment variables: RADARR_URL, RADARR_API_KEY, SONARR_URL, SONARR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Radarr And Sonarr Server's toolset — search_media, request_download, check_status and 1 more — is a fair guide to whether it matches your workflow. It is maintained by JasonTulp; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp radarr and sonarr server mcp server does with a few real requests.