qbittorrent-filebot

qbittorrent-filebot is intended to integrate qBittorrent with FileBot to automatically rename/move/downloaded media files based on metadata (e.g., using FileBot’s matching/renaming capabilities) when torrents complete.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Repo ↗ Automation media-management automation qBittorrent FileBot post-processing
⚙ Agent Friendliness
25
/ 100
Can an agent use this?
🔒 Security
28
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
0
Error Messages
0
Auth Simplicity
90
Rate Limits
0

🔒 Security

TLS Enforcement
30
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
30
Secret Handling
30

No repository-level security details were provided. Typical risks for this class of integrations include: exposure of qBittorrent/FileBot credentials in config files/environment variables, SSRF/local network access if HTTP callbacks are used, and risk of executing shell commands for post-processing—so least-privilege and secret hygiene are important. Scores are low-to-unknown due to missing observable evidence.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
40
Error Recovery
20
AF Security Reliability

Best When

You already have qBittorrent and FileBot running and want automated library organization on torrent completion.

Avoid When

You need a fully managed service with guaranteed uptime/SLA or a well-defined public REST/SDK interface from this package itself.

Use Cases

  • Automate post-processing of torrent downloads (rename/move to library folders)
  • Improve media organization in a Plex/Jellyfin/Emby-style setup
  • Standardize naming of TV/movies from torrent filenames using metadata from FileBot

Not For

  • Manual one-off renaming without automation
  • Users who don’t run both qBittorrent and FileBot
  • Environments requiring a hosted, managed SaaS API (this is an integration/tooling package)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No auth details were provided in the supplied information, so this is assessed as not applicable/unknown based on lack of observable interface/auth documentation.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; likely self-hosted tooling.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Integration packages like this often depend on local services and configuration (qBittorrent/FileBot), so agent automation may fail without careful environment setup.
  • Idempotency and safe re-processing behavior may be unclear for file-renaming/moving; repeated runs can cause conflicts or duplicate moves if not explicitly handled.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for qbittorrent-filebot.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered