FluxDown

What zerx-lab/FluxDown MCP server does

zerx-lab/FluxDown connects an MCP client to the FluxDown download manager. It gives an agent controls for creating download tasks, checking their progress, changing task state, and deleting tasks. Supported task inputs include HTTP and HTTPS URLs, FTP locations, magnet links, and BitTorrent downloads. FluxDown itself also supports eD2K, HLS, and DASH through its broader download engine.

The MCP interface also exposes operational information around downloads. An agent can inspect named queues and their configuration, list RSS subscriptions, create a feed subscription with scheduled polling, or remove a subscription together with the items it collected.

How it works

FluxDown uses a Rust and Tokio download engine with persisted task state. Its broader deployments use SQLite with WAL by default, while server deployments can use PostgreSQL. Persisted state allows downloads to recover and resume after interruption.

The MCP layer is part of FluxDown’s built-in automation and API surface. FluxDown can run as a desktop application, a headless server, or a containerized service, with the same download engine shared across its clients. The server-side distribution includes fluxdown-agent --server and fluxdownd, plus an embedded web interface.

Setup and configuration

Install the latest FluxDown build from GitHub Releases or fluxdown.com, or use the server distribution for a headless deployment. The project provides packages for Windows, macOS, Linux, Android, and several NAS environments, as well as a Docker image named ghcr.io/zerx-lab/fluxdown-server.

For a Docker deployment, the supplied Compose configuration starts the service with:

docker compose -f docker/docker-compose.yml up -d

The default server address is 0.0.0.0:17800, and the web interface is available at http://<server>:17800/. Configure an access key during first-run setup before exposing the service. The key must be 8–128 visible ASCII characters and include at least one letter and one digit. For unattended initialization, FLUXDOWN_TOKEN can be supplied through the deployment environment or a secret manager; it initializes the key only when one has not already been configured. FLUXDOWN_BIND changes the bind address.

Persist /data for the database, logs, and access key, and persist /root/Downloads for downloaded files. Use an HTTPS reverse proxy for remote access and keep the service on a trusted network during initial setup.

Tools and capabilities

• download_add creates HTTP/HTTPS, FTP, magnet, or BitTorrent tasks.
• download_list returns task progress, speed, and status, with an optional status filter.
• download_get retrieves one task by ID.
• download_pause pauses or resumes one task.
• download_pause_all pauses or resumes all tasks.
• download_remove removes a task and can optionally delete its downloaded files.
• queue_list reports named queues and their configuration.
• rss_list reports RSS subscriptions, configuration, and runtime state.
• rss_add subscribes to an RSS feed and starts scheduled polling.
• rss_remove deletes a subscription and the items it collected.

Limitations and notes

Removing a task can also delete its downloaded files, so agents should treat that option as destructive. RSS subscriptions can collect items automatically according to their polling schedule. FluxDown’s local downloads do not require a FluxCloud account, but the application can send anonymous installation and daily-active statistics unless analytics are disabled with analytics_enabled. Download and task information is not included in that telemetry.