AI-IDM MCP Server
Related Servers
Alternatives to AI-IDM MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- 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.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to manage a local SQLite task backlog over stdio, with tools to create, search, list, get, update, and stat tasks while preserving audit history and idempotency.MIT
- FlicenseNot gradedqualityAmaintenanceExposes 17 scraping tools over stdio or SSE so an LLM agent can drive fetching, extraction, screenshotting, and full crawls of hostile, bot-protected sites through conversation.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and filter titles, browse rankings, read comments, manage favorites, download albums, chapters, and covers with live progress, cancellation, and retry, and convert downloads into ZIP, PDF, or long images, all through natural language. Exposes 21 tools and 3 knowledge resources over stdio, SSE, and HTTP transports, along with runtime configuration and account login.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to control an anti-detection browser for navigation, interaction, search, extraction, downloads, session reuse, and multi-tab or batch workflows over stdio or HTTP.201 npmMIT
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.