
Oraclarr
io.github.bdog720由 GitHub 帳號 bdog720 發布v2.0.3更新於 Oct 30, 2026
Read-only-by-default MCP server for diagnosing a self-hosted arr stack (Sonarr, Radarr & more).
概覽
預設唯讀的 MCP 伺服器,讓助理在同一處診斷自架的 Sonarr、Radarr 等媒體下載堆疊。
- 可以做什麼
- 檢查各服務健康狀態、下載佇列、停滯項目,以及某部作品在流程中的位置
- 解釋抓取決策、品質設定、自訂格式與抓取歷史
- 查看缺少的項目、索引器、轉碼、即將上架內容與媒體庫狀態
- 讀取主機指標、Docker 容器狀態與日誌,以及執行中或失敗的工作
- 開啟寫入後,可選擇啟動重新整理、重新掃描、搜尋或重新命名
- 適用情境
- 適合執行自架 arr 媒體堆疊(Sonarr、Radarr、Prowlarr、qBittorrent、Jellyfin 等),並希望用自然語言詢問維運問題、不必在多個網頁介面間切換的人。常用於排查下載、品質判定、磁碟與主機壓力以及容器問題。
- 執行需求
- 透過 uvx 以 stdio 在本機執行(需 Python 3.12+ 與 uv),或以 Docker 容器提供 HTTP 服務。每個服務實例需填寫基礎 URL 與憑證:Sonarr、Radarr 等服務需 API 金鑰,qBittorrent 需使用者名稱與密碼。設定來自 ORACLARR_ 開頭的環境變數或選用設定檔,且需能連線到這些服務。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Oraclarr,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Oraclarr
Ask your media stack what's going on, in plain language.
A locally-run MCP server that lets an LLM client (Claude Code, Claude Desktop) diagnose a self-hosted *arr media stack. It only reads by default. Writes are opt-in and need a token.
What it does
Oraclarr gives a language model one place to answer the operational "why" questions that normally mean tabbing through six web UIs. It aggregates across your services and returns a single, structured answer without changing anything. One opt-in tool, start_job, can start a refresh, rescan, search or rename. See Writes.
Covered now: Sonarr, Radarr, Sportarr, Prowlarr, qBittorrent, Tdarr, Profilarr, Jellyfin, Cleanuparr, Netdata, TrueNAS and Docker, including multiple instances of the same type (a separate anime or 4K Sonarr/Radarr, say). Every tool fans out across all the instances you define and reports each one separately.
In practice
Once connected, you just ask. Oraclarr picks the right tool and answers:
Tools
Read-only by default, and outcome-oriented rather than one-per-endpoint, which keeps the model accurate. Only start_job writes, and only when you switch writes on:
Install
Two ways to run it. Pick one:
- 🐳 Docker (recommended). A small always-on container next to your arr stack. Works with Dockge, Portainer, Unraid and plain
docker compose. - 🐍 Python (uv). Runs directly on your machine with no container. Handy for local development, or if you don't use Docker.
Either way, every setting is an environment variable that starts with ORACLARR_. With Docker that means one .env file next to the compose file, and Dockge and Portainer show both in their editors. Start from .env.example. Configuration lists every variable. Your .env is never committed.
Option A: Docker (recommended)
Oraclarr runs as a long-running container that serves MCP over HTTP at http://<host>:7979/mcp. You need two files in one folder: docker-compose.yml and .env.
Using a stack manager (Dockge, Portainer, etc.): create a new stack, paste the compose below into the editor, and paste your settings into the stack's .env. Hit deploy. Portainer saves the variables from its web editor as stack.env, so in Portainer change the compose line to env_file: stack.env.
Using the command line:
This is the whole compose file. You don't edit it when you add or remove a service; that happens in .env:
Want container state and logs too (get_containers)? Use docker-compose.full.example.yml instead. It adds the read-only Docker socket proxy, the one sidecar that has to live in the same stack. Containers explains it.
Then connect your client: one command for Claude Code, a small JSON block for Claude Desktop, Cursor, Codex, VS Code, Gemini CLI or Windsurf.
Option B: Python (uv)
Run Oraclarr directly, no Docker. Requires Python 3.12+ and uv.
The package is on PyPI as oraclarr-mcp. It speaks MCP over stdio, so your client starts the process and passes the settings in its env block:
From a clone (for development): put the same ORACLARR_* lines in a .env in the repo folder (it's read at startup), then:
In a client config, use "command": "uv", "args": ["run", "python", "-m", "oraclarr_mcp"] and a "cwd" pointing at the repo.
Configuration
Each service is an instance with a name you choose. Its settings are variables named ORACLARR_<NAME>_<FIELD>, and an instance exists as soon as its _URL is set:
Underscores in the name become dashes in the instance name, so SONARR_ANIME shows up as sonarr-anime. Blank values count as unset, so you can keep lines for services you don't run. A misspelled ORACLARR_ variable stops the container with a message that names it, instead of failing quietly later.
Jellyfin needs an API key (Dashboard → API Keys). Cleanuparr needs its account API key (Settings → Account → API Key). TrueNAS, Netdata and Docker each have a short setup guide, linked below.
Server settings are optional:
Every tool call has a time budget. If an instance doesn't answer in time, it comes back as status: "timeout" and the other instances still return their data. List results carry only the useful fields and stop at each tool's limit; when there is more, truncated and total say so. API keys and passwords show up as *** in responses and log lines.
Guides
- Connecting a client: Claude Code, Claude Desktop, Cursor, Codex CLI, VS Code, Gemini CLI and Windsurf, the token header, and why not to use a cloud connector.
- Host metrics: the TrueNAS read-only user and the Netdata container for
get_host. - Containers: the Docker socket proxy for
get_containers, and what it lets through. - Writes: the two switches, the token, the two-step plan flow, and the audit log.
- The config file: using
config.yamlinstead of (or as well as).env, and migrating off it. - Upgrading: what to change when you cross a particular version.
Roadmap
Oraclarr is built in phases. It is read-only by default, and write capability arrives behind explicit safety gates. The architecture (typed clients + outcome tools + config-selectable toolsets) is designed to extend to other self-hosted suites beyond *arr, too.
- ✅ Phase 1: read-only diagnostics. Sonarr, Radarr, Sportarr, Prowlarr, qBittorrent, Tdarr, Profilarr, Jellyfin, Cleanuparr, TrueNAS, Netdata, Docker.
- 🔜 Phase 2: more services, still read-only. Seerr, Gluetun, Unpackerr, ntfy. The architecture also opens up to non-*arr stacks.
- 🚧 Phase 3: safe write actions. Started in 2.0.0 with
start_job(refresh, rescan, search, rename and Jellyfin scans), gated behind two switches, a token, dry-run previews and an audit log. Retry and request approval come later. - 🔭 Phase 4: destructive actions. Delete media, blocklist, stack control and Cleanuparr changes, behind an explicit confirmation and allowlist.
Have a service you'd like covered? Open an issue.
💬 Feedback & Issues
Found a bug or have a feature request? Please open an issue on GitHub.
🤝 Contributing
Issues and PRs welcome. The codebase is TDD throughout:
Adding a service follows a small recipe (new client → register by type → extend a tool → write the test). See the project layout under src/oraclarr_mcp/.
📄 License
Apache License 2.0. See LICENSE.
💖 Support the Project
If Oraclarr saves you from tabbing through six web UIs to work out why something didn't download, consider buying me a coffee.
來源:README.md,提交 e3d1014
工具
0版本歷史
6- v2.0.3最新Oct 30, 2026
- v2.0.2Oct 13, 2026
- v1.7.0Oct 13, 2026
- v1.6.0Oct 12, 2026
- v1.3.0Oct 12, 2026
- v1.0.1Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分