prowlarr-mcp
Prowlarr용 MCP 서버입니다.
cd prowlarr-mcp
uv sync
cp .env.example .env.env에 PROWLARR_API_KEY를 설정하세요. API 키는 Prowlarr의 Settings → General → Security 경로에서 확인할 수 있습니다.
구성:
변수 | 기본값 | 설명 |
|
| URL 기본 경로를 포함한 Prowlarr 기본 URL |
| 필수 | Prowlarr API 키 |
|
| HTTP 타임아웃, 0보다 크고 최대 300초 |
|
|
|
Related MCP server: MCP *arr Server
uv run prowlarr-mcpCodex/OpenCode 스타일 stdio 구성 예시:
{
"command": "uv",
"args": [
"--directory",
"/path/to/prowlarr-mcp",
"run",
"prowlarr-mcp"
]
}search_releases는 다음을 허용합니다:
query: 텍스트 검색어. 빈 문자열은 최신 릴리스를 요청합니다.
search_type: search, tvsearch, movie, music, 또는 book.
indexer_ids: 선택적 Prowlarr 인덱서 ID.
categories: 선택적 Newznab 카테고리 ID.
limit: 결과 수. 기본값은 20이며 구성에 따라 상한이 적용됩니다.
offset: 음수가 아닌 결과 오프셋.
응답은 의도적으로 Prowlarr의 전체 ReleaseResource보다 작지만, 향후 다운로드 제출 워크플로를 위해 indexer_id와 guid를 유지합니다. Prowlarr는 limit을 여러 인덱서에 독립적으로 적용할 수 있으므로 MCP 서버도 결합된 응답에서 이를 적용합니다. truncated는 MCP 서버가 수신한 응답의 일부를 버렸다는 뜻이며, has_more 페이지네이션 표시기가 아닙니다. 따라서 Prowlarr에 추가 결과가 있는지 증명할 수 없습니다.
v0.1: 구성된 Prowlarr 인덱서를 통해 릴리스 검색.
사용 가능한 인덱서와 검색 카테고리 탐색.
선택한 릴리스를 구성된 다운로드 클라이언트에 제출.
Prowlarr 상태, 인덱서 상태, 검색 기록 확인.
이 저장소에는 서버를 실행하고 하나의 도구를 호출하는 범용 stdio 클라이언트가 포함되어 있습니다.
uv run src/prowlarr_mcp/scripts/mcp_client.py \
--command "uv run prowlarr-mcp" \
--method "search_releases" \
--arguments '{"query": "yani neko"}'서버 명령을 다른 디렉터리에서 실행해야 하면 --cwd를 사용하고, 기본 60초 도구 호출 타임아웃을 재정의하려면 --timeout을 사용하세요. 스크립트는 구조화된 도구 출력을 JSON으로 출력하며, 잘못된 입력, 연결 실패 또는 MCP 도구 오류가 발생하면 0이 아닌 코드로 종료합니다.
uv run ruff format --check .
uv run ruff check .
uv run pyrefly check
uv run python -m unittest discover -s testsSearch enabled Prowlarr indexers for Torrent or Usenet releases.
An empty query requests recent releases. Omit indexer_ids and categories to search all enabled indexers and categories. Results preserve Prowlarr's ordering. The indexer_id and guid identify a release for a future download submission capability, which is not available in version 0.1.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| offset | No | ||
| categories | No | ||
| indexer_ids | No | ||
| search_type | No | search |
| Name | Required | Description |
|---|---|---|
| limit | Yes | |
| query | Yes | |
| offset | Yes | |
| releases | Yes | |
| returned | Yes | |
| truncated | Yes | |
| search_type | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds meaningful behavioral context beyond annotations: results preserve Prowlarr ordering, empty queries mean recent releases, and indexer_id plus guid are not yet usable for downloads. It does not contradict the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact: three short sentences that front-load the main action and then add behavioral clarifications. The future-download-availability caveat is a small but relevant addition that prevents the agent from assuming a download capability that doesn't exist in this version. No sentence is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple parameter set, no required parameters, a complete output schema, and safety annotations, this description covers everything needed to call the tool correctly. An agent can understand the search scope, the empty-query special case, filtering by indexers/categories, and the result-ordering guarantee.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description compensates by explaining the key query semantics: empty query means recent releases, and omitted indexer_ids/categories search all enabled ones. It does not explicitly describe limit, offset, or search_type, but those are straightforward from the schema defaults and the enum values. This is strong semantic coverage despite a few remaining gaps.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence states a specific action ('Search'), a specific resource ('enabled Prowlarr indexers'), and the result domain ('Torrent or Usenet releases'). The empty-query and omit-filter explanations further clarify the scope. Although there are no sibling tools to differentiate from, the purpose is unambiguous and complete.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly tells the agent when behaviors change: an empty query requests recent releases, and omitting indexer_ids and categories searches all enabled indexers and categories. There are no sibling tools to compare against, so the lack of alternatives guidance is acceptable; the exclusion of download submission capability is also useful context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0search_releasesScored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose is clearly focused on searching releases, making misselection unnecessary.
search_releases follows a clean verb_noun naming convention. With a single tool there is no conflicting pattern, and the name accurately describes the operation.
A single tool is slightly thin for a server named Prowlarr, but it is appropriate for the currently advertised search-only capability. The missing functionality is explicitly reserved for a future version, so the count is reasonable, not excessive.
The search tool offers robust coverage for querying, filtering by categories or indexer_ids, and fetching recent releases. However, there is no way to discover available indexer_ids or continue from a search result to download submission, and the description explicitly notes that capability is unavailable, leaving a meaningful workflow gap.
Search the tool catalog. Customer API key required. Catalog metadata is not a security guarantee.
Search OpenAlex papers, authors, institutions and citations. Hosted on Apify; needs an Apify token. Send your own Apify API token as an Authorization: Bearer header.
Search website motion, specs and recreation packs. Account required; OAuth or bearer API key.
Search a curated directory of agent tools, MCP servers, APIs, protocols and skills. No auth.