{"id":"ghostserverd-qbittorrent-filebot","name":"qbittorrent-filebot","homepage":"https://hub.docker.com/r/ghostserverd/qbittorrent-filebot","repo_url":"https://hub.docker.com/r/ghostserverd/qbittorrent-filebot","category":"automation","subcategories":[],"tags":["media-management","automation","qBittorrent","FileBot","post-processing"],"what_it_does":"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.","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)"],"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.","alternatives":["FileBot’s own automation/scheduler features","Post-processing scripts in qBittorrent (custom scripts)","Other media automation stacks (Sonarr/Radarr + indexers + rename/quality profiles)"],"af_score":25.0,"security_score":28.0,"reliability_score":25.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:56:45.093775+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; likely self-hosted tooling."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":25.0,"security_score":28.0,"reliability_score":25.0,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":0.0,"tls_enforcement":30.0,"auth_strength":30.0,"scope_granularity":20.0,"dependency_hygiene":30.0,"secret_handling":30.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":40.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}