autobrr-mcp
MCP server exposing autobrr's full API as tools, enabling LLMs to read and manage filters, indexers, feeds, clients, actions, releases, and system config. It wraps approximately 104 endpoints into 13 resource-scoped tools for comprehensive autobrr instance management.
README
autobrr-mcp
Part of the arr-mcps collection. MCP server exposing autobrr's API as tools, so an LLM can read and manage a full autobrr instance: filters, indexers, IRC networks, RSS/Torznab feeds, download clients, actions, release queue and stats, import lists, notifications, API keys, proxies, and system config.
Built with FastMCP. autobrr's API has no OpenAPI
spec, so the endpoint table is hand-maintained against autobrr's
internal/http handlers (see AGENTS.md).
Creating an API key
Create a key in autobrr Settings > API Keys. The token is shown once at
creation; the server sends it as the X-API-Token header on every request.
Install
Download a wheel from the latest release
and install it as a uv tool (no repo checkout needed):
uv tool install autobrr_mcp-*.whl
This puts an autobrr-mcp command on your PATH. Register it with Claude Code:
claude mcp add autobrr \
--env AUTOBRR_URL=https://autobrr.example.com \
--env AUTOBRR_API_KEY=<key> \
-- autobrr-mcp
From source
uv sync
cp .env.example .env # fill in AUTOBRR_URL and AUTOBRR_API_KEY
claude mcp add autobrr \
--env AUTOBRR_URL=https://autobrr.example.com \
--env AUTOBRR_API_KEY=<key> \
-- uv run --directory /path/to/autobrr-mcp autobrr-mcp
Config
| Env var | Required | Default |
|---|---|---|
AUTOBRR_URL |
yes | - |
AUTOBRR_API_KEY |
yes* | none (no auth header sent if unset) |
* Every autobrr API endpoint requires a token; set it or every call returns
401. The server still starts without one so errors surface from the API rather
than at startup. If your autobrr instance is served under a base URL (e.g.
https://host/autobrr/), include that subpath in AUTOBRR_URL.
Tools
Thirteen resource-scoped tools. Each takes an operation (one of the listed
endpoints) plus an arguments dict matching that operation's parameters, and
dispatches to the underlying endpoint. This is the fleet's portmanteau
pattern: ~104 autobrr endpoints wrapped as 13 tools so every session's
system prompt stays small.
| Tool | Operations (endpoints) |
|---|---|
autobrr_filters |
list, create, get, update, update_partial, delete, duplicate, toggle_enabled, get/update notifications (/api/filters, /api/filters/{id}/...) |
autobrr_indexers |
list, list_schemas, list_options, create, get, update, delete, test_api, toggle_enabled (/api/indexer) |
autobrr_irc |
list/create/get/update/delete networks, create channel, send_cmd, restart, message history, process announce (/api/irc) |
autobrr_feeds |
list, create, get, update, delete, delete_cache, test, fetch_caps, get_latest, force_run, toggle_enabled (/api/feeds) |
autobrr_download_clients |
list, create, update, test, get, delete, get_arr_tags (/api/download_clients) |
autobrr_actions |
list, create, update, delete, toggle_enabled (/api/actions) |
autobrr_lists |
list, create, update, delete, refresh_all, refresh_one (/api/lists) |
autobrr_notifications |
list, create, get, update, delete, test, get_pushover_sounds (/api/notification) |
autobrr_api_keys |
list, create, delete (/api/keys) |
autobrr_proxy |
list, create, get, update, delete, test (/api/proxy) |
autobrr_release |
list, recent, get, stats (+activity/volume/heatmap/top indexers/top filters), indexer options, delete, retry action, duplicate profiles, cleanup jobs CRUD/toggle/run (/api/release) |
autobrr_config |
get, update (/api/config) |
autobrr_system |
healthz liveness/readiness, log files, latest update, check updates (read-only) |
Excluded on purpose: /api/auth (session/OIDC, not usable over an API
token), /api/events (SSE stream), the inbound /api/webhook list-trigger
routes, and /api/logs/files/{file} (raw log download).
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 AUTOBRR_URL/AUTOBRR_API_KEY; write tests need AUTOBRR_WRITE_TESTS=1) |
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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。