CellarTracker vs FluxDown
A side-by-side look at the CellarTracker and FluxDown MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CellarTracker for other tools and integrations work as a local process; choose FluxDown for other tools and integrations over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CellarTracker when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CT_USERNAME, CT_PASSWORD.
Choose FluxDown when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
download_add, download_list, download_get.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 43/100 · Fair | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CT_USERNAMECT_PASSWORD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 4,973 |
| Directory activity | 0 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View CellarTracker | View FluxDown |
Tools & capabilities
CellarTracker tools
No tool names declared yet. Check the project README from the listing page.
FluxDown tools 10
download_addCreate a download task (HTTP/HTTPS, FTP, magnet, BitTorrent)download_listList tasks with progress/speed/status, optional status filterdownload_getGet a single task by IDdownload_pausePause / resume one taskdownload_pause_allPause / resume all tasksdownload_removeRemove a task, optionally deleting downloaded filesqueue_listList named queues and their configurationrss_listList RSS subscriptions with their configuration and runtime staterss_addSubscribe to an RSS feed and start polling it on a schedulerss_removeDelete an RSS subscription and the items it collected
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
CellarTracker
{
"mcpServers": {
"cellartracker": {
"command": "npx",
"args": [
"-y",
"local-resolution"
],
"env": {
"CT_USERNAME": "YOUR_CT_USERNAME_HERE",
"CT_PASSWORD": "YOUR_CT_PASSWORD_HERE"
}
}
}
}
FluxDown
{
"mcpServers": {
"zerx-lab-fluxdown": {
"url": "http://127.0.0.1:17800/mcp"
}
}
}
Frequently asked questions
CellarTracker is categorized under Other Tools and Integrations and uses a local stdio subprocess. FluxDown belongs to Other Tools and Integrations and uses a remote HTTP/SSE transport. Pick CellarTracker for other tools and integrations work and FluxDown for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
CellarTracker has no declared pricing — check the project's own site. FluxDown is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cellartracker and zerx-lab-fluxdown as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CellarTracker has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 7 GitHub stars. FluxDown has 64/100 (Good) with 10 views, 0 installs and 4,973 GitHub stars.