AI-IDM MCP Server
Related Servers
Alternatives to AI-IDM MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA download manager for humans and AI with a native MCP server: add_task, list_tasks, wait_for_task with progress notifications from any MCP host. Multi-threaded multi-mirror HTTP, BT/magnet, 1000+ video sites (yt-dlp), RSS, token-secured remote Web UI. ~8MB, open source.12,308,725 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents and CLI tools to dispatch downloads through Chrome's native download engine over the MCP protocol, automatically inheriting browser cookies, login sessions, and proxy settings. Supports submitting, monitoring, pausing, resuming, and cancelling download tasks locally without manual server setup.8MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible agents to queue, inspect, pause, resume, and remove downloads by exposing aria2's JSON-RPC API as a focused set of tools.8MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLM agents to drive full web crawling and scraping through conversation by exposing tools for fetching, extracting, crawling, and screenshotting over stdio or SSE.-

HuntAPI MCP Serverofficial
AlicenseBqualityBmaintenanceEnables MCP clients to download video and audio from public media URLs, extract their metadata, and poll async jobs for progress and results, plus check account usage and credit balance. Runs locally over stdio or self-hosted Streamable HTTP with per-request API key authentication.7277 npmMIT- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, browse rankings, view album details and comments, manage favorites, and download manga albums or individual chapters asynchronously with progress tracking, cancellation, and retry. Also supports post-processing downloads into ZIP/PDF/long images, dynamic configuration updates, account login with cookie persistence, and access to schema/reference knowledge resources over stdio, SSE, and HTTP transports.-
TDQS
Scored across 12 tools
The set cleanly separates session download management (start/status/wait/cancel/list) from persistent queue management (queue_*), and download_hls is distinct. However, download_status called without an id overlaps heavily with list_downloads, and start_download vs queue_add require reading descriptions to distinguish immediate vs deferred execution.
All names are snake_case and the queue_* group is perfectly consistent (queue_add/run/list/remove/retry). The download group mixes noun-first (download_status, download_hls) with verb-first (start_download, cancel_download, wait_download, list_downloads), a minor but noticeable deviation.
12 tools is well within the ideal 3-15 range and each tool earns its place across probe, session tasks, persistent queue, and HLS handling. No tool appears redundant enough to prune beyond the noted status/list overlap.
The download lifecycle is fully covered: probe before download, start/status/wait/cancel, list, persistent queue with add/run/list/remove/retry, and HLS with bitrate/decryption/resume support. No obvious dead ends for a download manager domain.