SABnzbd MCP
Related Servers
Alternatives to SABnzbd MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables users to control and monitor NZBGet Usenet downloads through natural language using MCP-compatible clients. It provides 17 tools for managing download queues, tracking history, and adjusting server settings like speed limits.151MIT
- AlicenseBqualityBmaintenanceEnables control and management of a self-hosted media stack (Radarr, Sonarr, Prowlarr, SABnzbd, qBittorrent) through natural language via MCP.15GPL 3.0
- AlicenseAqualityAmaintenanceEnables interaction with SABnzbd (usenet) and qBittorrent (torrent) download clients through their APIs. Each client is optional and only tools for configured clients are registered.10MIT
- AlicenseBqualityCmaintenanceEnables managing a Sonarr TV show instance through natural language, including series and episode management, download queue monitoring, calendar tracking, and configuration of quality profiles and root folders.24MIT
- AlicenseAqualityBmaintenanceEnables natural-language clients to manage a personal torrent queue pipeline, including IMDb list candidate discovery, OMDb title lookups, Jackett indexer search, and qBittorrent RSS queue operations.18MIT
- AlicenseAqualityCmaintenanceEnables interaction with the *arr media management suite (Sonarr, Radarr, Lidarr, Prowlarr, SABnzbd) and TRaSH Guides through MCP tools, allowing media library management, searching, and configuration via natural language.706 npm1MIT
TDQS
Scored across 21 tools
Every tool targets a distinct operation on SABnzbd resources (queue, history, categories, etc.), with clear descriptions. Overlapping concerns like pause_queue vs pause_post_processing are properly differentiated.
All tools use a consistent verb_noun pattern with underscores and same stylistic choices (e.g., pause_queue, resume_queue, retry_download, set_speed_limit). No mixing of conventions.
21 tools cover the full SABnzbd interaction surface without excess. Each tool serves a clear purpose, and the number is well-balanced for a download manager API.
The tool set covers the complete lifecycle: adding NZBs, managing queue/history, controlling downloads and post-processing, and retrieving status information. No obvious missing operations for standard usage.