Prowlarr (Indexers) MCP. Manage your entire Usenet/Torrent stack from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Prowlarr (Indexers) MCP Server manages your entire Usenet and Torrent indexer setup through natural conversation with your AI agent. List all configured sources, check instant health status across the board, and manage credentials without opening a web UI.
It lets you add new indexers using templates or update existing ones on the fly. This is critical for maintaining media automation stacks.
What your AI agents can do
Add indexer
Adds a new indexer after you use get_indexer_schema to find the correct required fields.
Delete indexer
Removes an existing, configured indexer from your list.
Get indexer
Retrieves specific details for one particular indexer using its ID.
Retrieves a list of every indexer currently set up in your Prowlarr instance, along with their unique IDs.
Pings all connected indexers to determine if they are online and responding correctly.
Adds a brand-new indexer, guiding you through the necessary fields and templates to ensure correct setup.
Modifies credentials or URLs for an already configured indexer without deleting and re-adding it.
Fetches the specific template fields (e.g., Newznab, Torznab) needed to correctly format a new indexer entry.
Runs a live test on an indexer's credentials and URL combination to confirm it works before you save the changes.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Prowlarr (Indexers) MCP Server: 8 Tools for Indexer Management
Use these eight specialized tools to list, check the status of, add, modify, and delete all indexer sources in your Prowlarr instance via conversation.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Prowlarr (Indexers) on Vinkius019e38dbadd indexer
Adds a new indexer after you use `get_indexer_schema` to find the correct required fields.
019e38dbdelete indexer
Removes an existing, configured indexer from your list.
019e38dbget indexer
Retrieves specific details for one particular indexer using its ID.
019e38dbget indexer schema
Provides the necessary field templates and required input types for any supported indexer type (e.g., Newznab, Torznab).
019e38dbget indexer status
Checks the live connection status of all configured indexers to flag immediate issues.
019e38dblist indexers
Pulls a comprehensive list of every indexer currently active in your Prowlarr instance.
019e38dbtest indexer
Validates an indexer's URL and credentials against the API to ensure it works before saving changes.
019e38dbupdate indexer
Changes settings—like keys or URLs—for an indexer without having to delete and re-add it.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Prowlarr (Indexers), then connect any of our 4,900+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,900+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Prowlarr. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Checking if an indexer works shouldn't require logging into a separate dashboard.
Today, finding out why a download stopped is painful. You have to open the Prowlarr web UI, navigate to the sources tab, and then manually check the health indicator for every single indexer you run. If there are twenty of them, that's twenty individual checks—a slow process that wastes time when you need answers fast.
With this MCP server, you simply ask your agent: 'What's wrong with my indexers?' The agent runs `get_indexer_status` and instantly returns a clean list. It doesn't just say 'failed'; it tells you *what* failed (e.g., connection timeout) and exactly which source ID needs attention.
Prowlarr (Indexers) MCP Server: Add Indexer Configurations
Before, adding a new indexer meant hunting through documentation to figure out if it needed Newznab or Torznab fields. You'd guess the schema, run the tool, and then fix 5 errors because you missed a required parameter like `baseUrl` or failed to format the JSON correctly.
Now, just ask for the template using `get_indexer_schema`. The agent gives you the exact structure needed. Once you provide the keys, it handles the rest—it validates everything with `test_indexer` before finally committing the source via `add_indexer`. It's foolproof.
What you can do with this MCP connector
You're gonna connect your Prowlarr instance to any AI agent and you'll run indexer management straight from your workspace. Forget having to jump between five different web UIs just to check an API key or see if a source is still alive. This server lets you manage every single Usenet and Torrent indexer setup through simple conversation with your agent.
It gives you full control over your media stack, letting you list all configured sources, instantly verify their health status across the board, and adjust credentials without ever opening a clunky web interface. You can even add brand-new indexers using templates or update settings on the fly. This is critical for keeping your automation running smooth.
Indexer Overview and Status Checks
- To see what you've got set up, use
list_indexersto pull a comprehensive list of every single indexer currently active in your Prowlarr instance. It pulls the name and unique ID for each one on the list. - If you need deep details on just one source, run
get_indexerby providing that specific indexer's ID to retrieve its full configuration data. - To check if all your sources are connected right now, call
get_indexer_status. This pings every configured indexer simultaneously, flagging any immediate connection failures or timeouts so you know exactly what broke before it stops your whole setup.
Adding and Setting Up New Sources
- You don't have to guess how to format a new source. You first call
get_indexer_schema. This tells you the exact required field templates and input types for any supported indexer type, like Newznab or Torznab. - Once you know what fields are needed, use
add_indexerto create the brand-new indexer source. The agent guides you through filling out those necessary fields using the schema it just provided.
Validation and Modification
- Before you ever save a new setup or change an existing one, run
test_indexer. This validates the indexer's URL and credentials against the API to confirm they work live. It prevents you from committing broken builds that waste your time. - If an API key expires or the URL changes, don't delete the whole thing. Use
update_indexerinstead. You change settings—like keys or URLs—for a specific indexer without having to go through the hassle of deleting and re-adding it entirely. - If you need to ditch a source completely, use
delete_indexer. This removes an existing, configured indexer from your list permanently.
This server means you manage everything in one spot. You tell the agent what you wanna do—like adding a new Torznab feed or updating old keys—and it handles the API calls for you.
019e38dc-1c2e-725d-ae80-50afde529a29 
How Prowlarr (Indexers) MCP Works
- 1 Subscribe to this server, providing your Prowlarr API key and base URL.
- 2 Your AI client connects. You ask for a status check or to list indexers via natural conversation.
- 3 The agent executes the required tool (e.g.,
get_indexer_status), retrieves the raw data, and presents the actionable summary back to you.
The bottom line is that your AI client handles all the API calls and error parsing so you don't have to switch context or read JSON payloads.
Who Is Prowlarr (Indexers) MCP For?
This is for media server admins, home lab enthusiasts, and DevOps engineers who hate clicking through multiple web dashboards. If your job involves keeping a complex torrent/usenet stack running 24/7, you need this. It lets you troubleshoot critical failures (like expired API keys) faster than manually logging into the Prowlarr UI.
Uses get_indexer_status to quickly identify which indexers have gone offline when a download fails, preventing manual investigation.
Automates the provisioning and testing of new indexer configurations using add_indexer and test_indexer within a structured workflow.
Manages their entire media automation stack from one chat window, checking status or updating keys without leaving their primary terminal or client.
What Changes When You Connect
- Stop guessing if an indexer is down. Instead of having to open the Prowlarr GUI, run
get_indexer_statusand get a clean summary showing which sources are failing right now. This saves time when downloads stall unexpectedly. - Add complex indexers without error. Use
get_indexer_schemafirst. It gives you the exact fields required for Newznab or Torznab, so your AI agent knows exactly how to format the JSON payload when runningadd_indexer. - Handle credential rotation on the fly. When an API key expires, don't delete and re-create the indexer. Just run
update_indexerwith the new credentials. It handles the change cleanly. - Guarantee data integrity before deployment. Running
test_indexervalidates the connection live. This means you can confidently update settings knowing that the source will actually connect, preventing broken automation runs. - Keep your workflow contained. You never have to leave your primary chat environment. Listing sources with
list_indexers, checking status, and adding new ones all happen within one conversation thread.
Real-World Use Cases
The Indexer is failing sporadically.
A user notices downloads stopping across the board. Instead of opening Prowlarr and clicking through every source, they ask their agent to check the status. The agent runs get_indexer_status and immediately reports that 'RARBG' has a connection timeout, telling them exactly which tool (update_indexer) needs attention.
Adding support for a new content source.
A user finds a new torrent indexer. They first ask the agent to run get_indexer_schema to see what fields are needed (e.g., 'Torznab'). Once they gather the required API key and URL, the agent runs add_indexer, using the schema as a guide for perfect setup.
Cleaning up old or dead indexers.
The user reviews their list of sources. They ask to list_indexers to see all 20 entries. After confirming three are outdated, the agent executes delete_indexer, cleaning the stack in a few prompts rather than dozens of clicks.
Migrating API keys for compliance.
A major indexer changes its API key requirement. Instead of deleting and re-adding the source, the user asks the agent to update_indexer. The agent uses the existing ID and only swaps out the credential fields, minimizing disruption.
The Tradeoffs
Manual status checks.
Going into the web UI and manually refreshing the status for 10 different indexers one by one until they all show green. This is slow, tedious, and prone to human error.
→
Just ask your agent to run get_indexer_status. It checks everything at once and gives you a clean summary of successes and failures.
Guessing the required fields for new indexers.
Trying to add a Newznab source by guessing the template fields, leading to JSON formatting errors or missing mandatory parameters.
→
Always run get_indexer_schema first. It provides the exact templates and field names you need before you attempt to use add_indexer.
Updating indexers in chunks.
Running a mix of tools (e.g., calling get_indexer, then updating, then listing) without a clear goal, which results in confusing conversational output and lost context.
→ Define the scope: 'I need to update all credentials for my Usenet indexers.' Let your agent coordinate the necessary sequence of calls (e.g., list -> get details -> update).
When It Fits, When It Doesn't
Use this server if you manage a complex, multi-source media automation stack and spend time troubleshooting broken connections or stale API keys. The core value is unifying administrative tasks into conversational tool calls.
Don't use it just because you can list sources; that's only one part of the puzzle. You need to be comfortable with the lifecycle: knowing when to get_indexer_schema (before adding), when to test_indexer (before updating), and when to get_indexer_status (when troubleshooting). If your main pain point is simply viewing data, you might only need list_indexers. But if your problem involves changing or fixing the data, this collection of tools—especially the pairing of get_indexer_schema with add_indexer and test_indexer with update_indexer—is what you need. If your infrastructure is simple (e.g., only one indexer), the overhead might be overkill.
Common Questions About Prowlarr (Indexers) MCP
How do I check all my indexer sources using list_indexers? +
Run the list_indexers tool. It pulls every configured source ID and name into your chat window, letting you quickly see what's active without opening the UI.
What if my API key expires? Should I use update_indexer or add_indexer? +
You should always use update_indexer. This tool modifies the settings for an existing source using its ID. If you used add_indexer, it might create a duplicate entry, which is worse.
Does get_indexer_schema help me format new indexers? +
Yes, absolutely. It fetches the precise field templates required for specific types (like Newznab) so you know exactly what variables your agent needs to build the configuration.
Is there a way to check if an indexer is alive without affecting its settings? Use get_indexer_status. +
Yes, get_indexer_status runs a read-only health ping against all sources. It checks connectivity and status but does not alter any of your configured credentials or URLs.
How does running `test_indexer` differ from using `get_indexer_status`? +
The test runs a live handshake to confirm connectivity. While status checks for general uptime, the test_indexer tool verifies credentials and validates the entire connection flow against the remote service.
I want to remove an indexer. What precautions should I take when using `delete_indexer`? +
Before running delete_indexer, always use get_indexer first. This lets you confirm the exact ID and configuration details, ensuring you don't accidentally delete a critical source.
How can I pull all the current settings for just one indexer without listing every configured source? Use `get_indexer`. +
You simply provide the unique ID. This tool bypasses the list view and pulls every field—API endpoint, rate limits, etc.—for that single, specific entry.
What is the proper workflow for adding a new indexer using `add_indexer`? +
Start by calling get_indexer_schema. This provides templates and required fields. Then, use those exact fields to format your data before you call add_indexer; this prevents immediate setup errors.
How can I check if any of my indexers are currently down? +
You can use the get_indexer_status tool. It retrieves the current health status of all configured indexers, highlighting any errors or connection issues.
What is the best way to add a new indexer without knowing the JSON structure? +
First, run get_indexer_schema to see the templates for supported indexers. Once you have the correct fields, you can use add_indexer with the required data.
Can I verify my settings before applying them to an indexer? +
Yes! Use the test_indexer tool. It allows you to test the connection and configuration of an indexer before saving it, preventing broken setups.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.