aria2-mcp
Related Servers
Alternatives to aria2-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI agents to queue, monitor, probe, pause, resume, cancel, and speed-limit downloads, grab links from web pages, and manage download categories through a Windows download manager.MIT
- AlicenseNot gradedqualityAmaintenanceA download tool for AI agents that wraps aria2 with safety rules and MCP server support, enabling reliable downloads without false positives.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables an agent to submit magnet links to a Transmission daemon and monitor their download progress, including pausing, resuming, and listing torrents with verdicts like downloading, stalled, or complete.MIT
- AlicenseBqualityAmaintenanceEnables AI agents to drive a multi-connection download engine over stdio: probe URLs, start, monitor, wait on and cancel downloads, fetch HLS streams, and manage a persistent SQLite-backed queue. Agents can carry out instructions like downloading several URLs in parallel and reporting which ones failed.122MIT
- AlicenseNot gradedqualityCmaintenanceProvides 20 essential tools including HTTP requests, web search, file I/O, shell commands, and persistent memory for any MCP client, with zero configuration required.MIT
- AlicenseAqualityAmaintenanceMCP server exposing qBittorrent's WebUI API v2 as tools, enabling LLMs to manage torrents, categories, tags, RSS feeds, search plugins, and application settings.903MIT
TDQS
Scored across 8 tools
Each tool targets a distinct aria2 operation: add, remove, pause, unpause, list, status, global_stat, and get_version. Collection vs. single-download vs. aggregate reporting tools are clearly separated by their descriptions.
All tools share the aria2_ prefix and snake_case formatting, which is highly consistent. However, the verb/noun pattern is mixed: some are verbs (remove, pause, unpause, list), some are noun-only (status, global_stat), and some are verb_noun (add_uri, get_version).
Eight tools is well-scoped for an aria2 download management server. Each tool covers a core, non-redundant operation without excessive surface area.
The surface covers the core download lifecycle: add, pause, resume, remove, and query status/list/aggregate stats. Minor gaps exist for update/configuration operations (e.g., changing download or global options, session management) that agents could work around or that may be out of scope.