FluxDown
Allows adding, monitoring, and managing BitTorrent and magnet link downloads via the MCP server.
FluxDown
Downloads, Supercharged.
A blazing fast, multi-protocol download manager — the free & open-source IDM alternative.
Website · Download · Changelog · FAQ · Feedback
English | 简体中文
Highlights
Up to 10x faster — Rust + Tokio engine with IDM-style dynamic segmentation
Multi-protocol — HTTP/HTTPS, FTP, BitTorrent, eD2K, HLS & DASH streaming
Browser integration — Chrome / Edge / Firefox extension with a 3-layer interception engine
AI-agent ready — built-in MCP (Model Context Protocol) server: let Claude, Cursor & other AI clients manage your downloads
Resume anywhere — full download state persisted in SQLite; survive crashes and reboots
Beautiful UI — light/dark themes, 13 color schemes, responsive three-pane layout
Clean & private — free forever, no ads, no tracking, no account, local-first
Related MCP server: m3u8 MCP Server
Features
Feature | Description |
Rust-Powered Engine | Built on Rust and Tokio with zero-cost abstractions — memory-safe concurrency at maximum throughput |
Smart Segmentation | Segments split dynamically at runtime; idle threads rescue slow segments, just like IDM — but smarter |
Multi-Protocol | Dedicated engines for HTTP/HTTPS, FTP, BitTorrent (DHT/UPnP/magnet), eD2K (server + Kad DHT source finding, MD4 verification), HLS (AES-decrypt) and DASH |
Speed Control | Token-bucket global rate limiting — download in the background without killing your browsing |
Resume Anywhere | Every byte tracked in SQLite with WAL; power loss never costs you progress |
Browser Integration | Three-layer download interception, streaming media sniffing, Alt+Click bypass, right-click send |
MCP Server | Built-in Model Context Protocol endpoint (Streamable HTTP) with 9 tools — AI agents can add, monitor and control downloads |
Beautiful Interface | shadcn-style widgets, IDM-style segment visualization, named queues, system tray |
Clean & Private | Zero ads, zero telemetry lock-in, zero accounts — your data never leaves your machine |
FluxDown vs. IDM
FluxDown | IDM | |
Price | Free forever | $24.95 + renewals |
Open source | Yes (AGPL-3.0) | No |
Platforms | Windows / macOS / Linux | Windows only |
BitTorrent & magnet | Yes | No |
eD2K / eMule links | Yes | No |
HLS / DASH streaming | Yes | Partial |
Dynamic segmentation | Yes | Yes |
Browser extension | Chrome / Edge / Firefox | Yes |
Ads & tracking | None | — |
Installation
Grab the latest build from GitHub Releases or fluxdown.zerx.dev:
Platform | Packages |
Windows (x64 / ARM64) |
|
macOS (Intel / Apple Silicon) |
|
Linux (x64) |
|
Browser Extension
Install the extension so FluxDown takes over browser downloads automatically:
MCP Server (Model Context Protocol)
FluxDown ships a built-in MCP server so AI agents (Claude Desktop, Cursor, Cline, …) can manage downloads via the Model Context Protocol. It speaks Streamable HTTP (JSON-RPC 2.0 over a single POST /mcp) on the local API port — no extra process needed.
Endpoint:
http://127.0.0.1:17800/mcp(local-only by default)Auth: Bearer token (
Authorization: Bearer <token>orX-FluxDown-Token), shared with the management APIEnable: Settings → API Service → toggle MCP endpoint (a token is generated automatically); the headless server enables it by default
Tools (9)
Tool | Description |
| Create a download task (HTTP/HTTPS, FTP, magnet, BitTorrent) |
| List tasks with progress/speed/status, optional status filter |
| Get a single task by ID |
| Pause / resume one task |
| Pause / resume all tasks |
| Remove a task, optionally deleting downloaded files |
| List named queues and their configuration |
Client configuration
{
"mcpServers": {
"fluxdown": {
"url": "http://127.0.0.1:17800/mcp",
"headers": { "Authorization": "Bearer <your-token>" }
}
}
}The MCP layer is implemented in native/api/src/mcp.rs on top of the same ApiHost trait that powers the REST management API and aria2-compatible JSON-RPC.
Architecture
Flutter renders the UI; a zero-FFI Rust engine does the heavy lifting. The two talk through Rinf signals, and the browser extension connects via Native Messaging.
flowchart TD
EXT["Browser Extension (WXT)"] -->|Native Messaging| NMH["fluxdown_nmh"]
NMH -->|Named Pipe / Unix socket| HUB
UI["Flutter UI (shadcn_ui)"] <-->|Rinf signals| HUB["hub — FFI adapter"]
HUB --> ENGINE["fluxdown_engine"]
ENGINE --> HTTP["HTTP/HTTPS"]
ENGINE --> FTP["FTP"]
ENGINE --> BT["BitTorrent"]
ENGINE --> ED2K["eD2K"]
ENGINE --> HLS["HLS / DASH"]
ENGINE --> DB[("SQLite")]Layer | Tech | Path |
UI | Flutter + shadcn_ui | |
FFI bridge | Rinf (Dart ↔ Rust signals) | |
Download engine | Rust + Tokio (zero FFI deps) | |
Browser extension | WXT + TypeScript | |
Website | Astro + React |
Building from Source
Prerequisites: Flutter SDK · Rust toolchain · Rinf CLI
# Check your environment
rustc --version
flutter doctor
# Install the Rinf CLI (once)
cargo install rinf_cli
# Fetch dependencies & generate Dart bindings
flutter pub get
rinf gen
# Run in debug mode
flutter run
# Build a release
flutter build windows --release # or: macos / linux# Debian/Ubuntu
sudo apt-get install cmake ninja-build clang pkg-config \
libgtk-3-dev libayatana-appindicator3-dev libnotify-dev libsecret-1-dev patchelf zstd
# Arch Linux
sudo pacman -S cmake ninja clang pkgconf gtk3 libayatana-appindicator libnotify libsecret patchelf zstdThe NMH relay binary (fluxdown_nmh) is built automatically by CMake during flutter build. Distribution packages (AppImage / deb / Arch / portable) are produced by CI on every tag.
flutter test # Dart tests
cargo test -p fluxdown_engine # Rust engine tests
cargo test -p hub # FFI adapter testsContributing & Community
Bug reports / feature requests — GitHub Issues or the in-app feedback dialog
QQ Group — 832143651
Pull requests are welcome! Before submitting, please make sure:
cargo fmt --check && cargo clippy -- -D warnings # Rust
flutter analyze # DartLicense
Distributed under the GNU Affero General Public License v3.0.
If FluxDown saves you time, consider giving it a Star — it helps more people discover the project.
Made by zerx-lab
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zerx-lab/FluxDown'
If you have feedback or need assistance with the MCP directory API, please join our Discord server