# Prowlarr (Indexers) MCP for AI Agents AI Agent Connect

> Prowlarr (Indexers) MCP lets you manage your Usenet and Torrent indexers through your AI agent. You can list your current indexers, check if they're online, add new ones, and test credentials without leaving your chat window. It's built for anyone who wants to handle media automation without constantly refreshing the Prowlarr web UI.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_YJA8MEahfmbqAYxGi0b2ZK8MPozB4BLo9MXVWOaD/ai-agent-connect
- **Tags:** prowlarr, indexers, usenet, torrents, media-automation

## Description

Managing a media stack usually feels like a chore. You're constantly jumping between tabs, copying API keys from one site to another, and refreshing the Prowlarr dashboard to see if your indexers actually stayed online. It's tedious and makes it easy to miss a single broken connection that stops your content from flowing. This Connector changes that by letting you handle those tasks through a simple conversation. Instead of digging through menus to find a specific Newznab or Torznab configuration, you just ask your agent to pull up the details or check the health of your entire fleet. You can grab the exact schema you need to add a new source, test the connection to make sure the credentials actually work, or swap out an old indexer for a new one on the fly. It's a way to keep your media stack running smoothly without the constant manual oversight. If you're looking for a way to manage these connections without the friction of a web interface, you'll find this Connector in the Vinkius catalog. It turns complex configuration tasks into simple commands, so you can spend less time troubleshooting and more time enjoying your media.

## Tools

### get_indexer
Get the specific details and settings for a single indexer. This helps you see exactly how a source is configured.

### get_indexer_schema
Pull the required fields and templates for various indexer types like Newznab. You can use this to see what information you need to provide for a new source.

### get_indexer_status
Check if your indexers are online or reporting errors. This lets you spot connection issues across your whole fleet instantly.

### test_indexer
Verify that your credentials and URLs work before you commit the changes. It prevents you from saving broken configurations that stop your content.

### list_indexers
See a full list of every indexer currently configured in your Prowlarr instance. This gives you a quick overview of your entire setup.

### add_indexer
Create a new indexer using the correct schema fields. This makes it easy to bring new content sources into your stack.

### delete_indexer
Remove an indexer that is no longer working or needed. You can clean up your setup without navigating the web UI.

### update_indexer
Modify the settings for an indexer that already exists. This is useful for swapping out old URLs or updating API keys quickly.

## Prompt Examples

**Prompt:** 
```
Check if my indexers are all online.
```

**Response:** 
```
I've checked your indexer status. Here is the current health of your sources:

| Indexer Name | Status | Connection |
| :--- | :--- | :--- |
| **RARBG** | 🟢 Healthy | Connected |
| **1337x** | 🔴 Error | Timeout |
| **DrunkenSlug** | 🟢 Healthy | Connected |
| **NinjaCentral** | 🟢 Healthy | Connected |

It looks like **1337x** is having trouble. Would you like me to test its configuration or update the API key?
```

**Prompt:** 
```
What do I need to add a new Newznab indexer?
```

**Response:** 
```
To add a new **Newznab** indexer, you'll need to provide the following fields:

*   **baseUrl**: The main URL for the service.
*   **apiKey**: Your unique API key.
*   **categories**: A list of categories to include.

Once you have those details, just let me know and I can add it for you.
```

**Prompt:** 
```
List my indexers and show me which one has ID 3.
```

**Response:** 
```
I've retrieved your indexers. Here is the info for the one with ID 3:

**Indexer:** DrunkenSlug
**ID:** 3
**Type:** Torznab
**Status:** Healthy

Would you like to see the full list of all your indexers or do you want to make a change to this one?
```

## Capabilities

### List all current indexers
See your entire indexer setup in one quick glance.

### Check indexer health
Instantly identify which sources are offline or reporting errors.

### View specific indexer details
Get the exact configuration for any specific source in your list.

### Fetch indexer schemas
Pull the required fields for different types like Newznab or Torznab.

### Test indexer credentials
Verify that your URLs and keys work before you save the configuration.

### Add new indexers
Create and add new content sources to your media stack.

### Update existing indexers
Modify settings or update API keys for your current sources.

### Delete old indexers
Remove sources that are no longer needed from your list.

## Use Cases

### Fixing a broken connection
An admin notices a source is down and asks the agent to check the status of all indexers. The agent identifies a timeout and allows the admin to update the API key immediately.

### Adding a new source
A user wants to add a Newznab indexer. They ask for the schema, get the fields, and then have the agent add it using the correct format.

### Bulk health check
A home lab owner wants to make sure everything is running before they go to bed. They ask the agent to verify the health of all indexers.

### Quick configuration swap
A user needs to change the URL of a specific torrent indexer. They ask the agent to update the existing indexer with the new link.

## Benefits

- Stop hunting through menus by using list_indexers to see your entire setup in one glance.
- Fix broken connections faster by using get_indexer_status to identify exactly which source is down.
- Avoid configuration errors by using get_indexer_schema to see exactly what fields a new source needs.
- Save time on setup by using test_indexer to confirm your API keys work before you finish.
- Keep your library updated by using add_indexer to quickly bring in new content sources.
- Clean up your setup by using delete_indexer to remove old sources without navigating the web UI.

## How It Works

The bottom line is you get a voice-controlled dashboard for your media automation indexers.

1. Connect your Prowlarr instance by providing your URL and API Key.
2. Open your AI client like Claude or Cursor and start asking questions about your indexers.
3. Use your agent to perform actions like adding new sources or checking for connection errors.

## Frequently Asked Questions

**What can I do with the Prowlarr (Indexers) MCP?**
You can manage your Usenet and Torrent indexers using natural language. This includes listing your sources, checking if they are online, adding new ones, and updating credentials without using the web interface.

**How does Prowlarr (Indexers) MCP help my home lab?**
It lets you monitor the health of your media automation stack from your AI client. You can quickly spot which indexers are down and fix them without having to open multiple browser tabs.

**Can I use Prowlarr (Indexers) MCP to add new sources?**
Yes. You can ask your agent to pull the required schema for a new source and then have it add the new indexer to your Prowlarr instance for you.

**How do I troubleshoot broken indexers with Prowlarr (Indexers) MCP?**
Just ask your agent to check the status of your indexers. It will identify which ones are reporting errors, and you can then tell it to update the API keys or URLs for those specific sources.

**Does Prowlarr (Indexers) MCP support Newznab and Torznab?**
Yes, it supports the schemas for common indexer types like Newznab and Torznab, making it easy to add or configure those sources via your AI client.

**Can I test my API keys using Prowlarr (Indexers) MCP?**
Yes. You can have your agent test an indexer configuration before you save it. This ensures your credentials are correct and prevents broken configurations from staying in your list.

**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.