What can you do with this server?

This MCP server exposes Prowlarr's API as tools for an LLM, enabling full read/write management of a Prowlarr instance. Key capabilities: * System & Commands: Get system status, restart/shutdown, run commands (sync, backup, update), manage backups, view logs, tasks, health, API routes, and filesystem. * Indexers: List, create, update, delete, bulk-edit, test, view stats/schemas/categories, manage status and run actions. * Applications: Manage connected apps (Sonarr, Radarr, Lidarr, Readarr, etc.), their profiles, test connections, bulk operations, and sync indexers. * Download Clients: CRUD, test, bulk edit/delete, and run named actions. * Indexer Proxies: Manage HTTP/SOCKS5 proxies, test, and run actions. * Notifications: Manage notification connections (Discord, Telegram, etc.), test, and run actions. * Tags: CRUD plus usage details across components. * Configuration: Get/update host, UI, development, and download client configs; manage custom filters. * Search & History: Search across indexers or Newznab XML, download releases, push to download clients, ping server, and query paged history with filters.

How do I use prowlarr-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@prowlarr-mcp search for 'The Matrix' across all indexers" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

prowlarr-mcp

by arr-mcps

Overview Schema Source Related Servers Discussions Admin

Python

Remote

prowlarr-mcp

Part of the arr-mcps collection. MCP server exposing Prowlarr's API v1 (REST) as tools, so an LLM can manage your indexers, applications, download clients, indexer proxies, notifications, tags, and custom filters — plus run cross-indexer searches and issue system commands. The full API surface is covered, read and write.

Built with FastMCP.

Enabling the API on your Prowlarr server

Generate an API key in Prowlarr Settings > General (Authentication section). Every /api/v1 endpoint requires it, sent as the X-Api-Key header.

Related MCP server: profilarr-mcp

Install

Download a wheel from the latest release and install it as a uv tool (no repo checkout needed):

uv tool install prowlarr_mcp-*.whl

This puts a prowlarr-mcp command on your PATH. Register it with Claude Code:

claude mcp add prowlarr \
  --env PROWLARR_URL=http://localhost:9696 \
  --env PROWLARR_API_KEY=<key> \
  -- prowlarr-mcp

From source

uv sync
cp .env.example .env   # fill in PROWLARR_URL and PROWLARR_API_KEY

claude mcp add prowlarr \
  --env PROWLARR_URL=http://localhost:9696 \
  --env PROWLARR_API_KEY=<key> \
  -- uv run --directory /path/to/prowlarr-mcp prowlarr-mcp

Config

Env var	Required	Default
`PROWLARR_URL`	yes	-
`PROWLARR_API_KEY`	yes*	none (no auth header sent if unset)

* Every API endpoint requires auth; practically you must set it, but the server still starts without one so errors surface from the API rather than at startup.

Tools

10 resource-scoped tools, each covering multiple Prowlarr API v1 operations (116 total) via an operation parameter. Call a tool with operation set to one of its listed operations and an arguments dict matching that operation's parameters — the tool's own description (visible to your MCP client) lists every operation, its signature, and a one-line doc. This keeps the full API surface available while costing a fraction of the context budget of registering all 116 operations as separate tools.

Tool	Operations	Kind
`prowlarr_system`	27	reads + writes
`prowlarr_applications`	17	reads + writes
`prowlarr_indexers`	14	reads + writes
`prowlarr_config`	13	reads + writes
`prowlarr_download_clients`	11	reads + writes
`prowlarr_indexer_proxies`	9	reads + writes
`prowlarr_notifications`	9	reads + writes
`prowlarr_tags`	7	reads + writes
`prowlarr_search`	6	reads + writes
`prowlarr_history`	3	read-only

Example: prowlarr_indexers(operation="prowlarr_get_indexer", arguments={"id": 3}). Operation-level naming (prowlarr_<verb>_<resource>) is preserved as the operation value, so the full operation list is still discoverable from each group tool's description at runtime.

Development

make help  # list all commands

Command	Does
`make sync`	`uv sync`
`make test`	Offline tests - one per endpoint, mocked HTTP
`make test-integration`	Tests against the live instance (needs `PROWLARR_URL`/`PROWLARR_API_KEY`)
`make build`	Build wheel + sdist into `dist/`
`make bump-patch` / `bump-minor` / `bump-major`	Bump the version in `pyproject.toml` + `uv.lock`
`make clean`	Remove build artifacts

The release workflow (.github/workflows/release.yml) builds and publishes to Releases whenever a v* tag is pushed - so the usual flow is make bump-patch, commit, then tag and push.

The integration suite is read-only by default (a plain make test-integration never mutates your instance). Setting PROWLARR_ALLOW_WRITES=1 additionally runs a scratch Tag create+delete round-trip.

Available Tools

10 tools

prowlarr_applicationsA

prowlarr applications operations on Prowlarr. Pass operation and an arguments dict matching that operation's parameters.

prowlarr_application_action(name, body) — Run a named action on an application (e.g. sync indexers). body is the ApplicationResource to act on.
prowlarr_bulk_delete_applications(body) — Bulk-delete applications. body is an ApplicationBulkResource with ids.
prowlarr_bulk_update_applications(body) — Bulk-edit applications. body is an ApplicationBulkResource with ids plus optional tags/applyTags/enable to apply to all of them.
prowlarr_create_app_profile(body) — Create an app profile. body is an AppProfileResource (name, appIds, and per-app settings).
prowlarr_create_application(body, force_save=None) — Create an application. Pass the full ApplicationResource as body (fetch prowlarr_list_application_schemas for available providers and fields). force_save bypasses validation.
prowlarr_delete_app_profile(id) — Delete an app profile by id.
prowlarr_delete_application(id) — Delete an application by id.
prowlarr_get_app_profile(id) — Get a single app profile by id.
prowlarr_get_application(id) — Get a single application by id.
prowlarr_list_app_profile_schemas() — List app profile schemas describing the structure of each app profile form section.
prowlarr_list_app_profiles() — List app profiles (named groups of applications, added in Prowlarr 1.19+).
prowlarr_list_application_schemas() — List application provider schemas (what each application implementation accepts). Read this before creating/updating an application.
prowlarr_list_applications() — List all configured applications (Lidarr/Radarr/Sonarr/Readarr etc.) that indexers are synced to.
prowlarr_test_all_applications() — Test every configured application.
prowlarr_test_application(body, force_test=None) — Test an application connection without saving it. body is the ApplicationResource to test. force_test skips the cached-test check.
prowlarr_update_app_profile(id, body) — Update an app profile by id.
prowlarr_update_application(id, body, force_save=None) — Update an application by id. body is the ApplicationResource to save.