jdownloader-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYJD_EMAIL | Yes | Email for My.JDownloader account. | |
| MYJD_DEVICE | Yes | Device name of the JDownloader device. | |
| MYJD_PASSWORD | Yes | Password for My.JDownloader account. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_linksA | Add URLs to the linkgrabber. autostart=True moves them straight to the download queue once resolved. priority: HIGHEST..LOWEST. |
| add_containerA | Add a link container (container_type: DLC | RSDF | CCF) by its content. |
| list_linkgrabberA | List linkgrabber packages+links (online/offline status) and whether JD is still collecting. Use the 'uuid' fields to act on items. |
| list_downloadsA | List download-queue packages with progress_pct, speed, ETA, status, and save path ('saveTo'). The workhorse for polling. |
| statusA | Overall download-controller state and aggregate speed (bytes/s). |
| wait_forA | Bounded poll of one download package (cap 120s). Returns finished/failed/ still_running/not_found — re-call on still_running. |
| move_to_downloadsB | Promote resolved linkgrabber items to the download queue. |
| control_downloadsA | Global queue control. action: start | stop | pause | resume. |
| force_startA | Force the given items to download now, bypassing queue/connection limits. |
| set_priorityB | Set priority (HIGHEST..LOWEST) on items in the given stage (linkgrabber | downloads). |
| set_enabledB | Enable/disable items in the given stage (linkgrabber | downloads). |
| get_directoriesA | Per-package save paths + the default download folder + extraction settings (extension enabled, custom extract path). |
| set_download_dirC | Set the download directory for the given download-queue packages. |
| set_extractionC | Toggle the extraction extension and/or set a custom extract path. |
| removeB | Remove items from a list. from_disk=True (downloads only) also deletes the files from disk. |
| resetA | Reset download-queue items so they re-download from scratch. |
| raw_actionA | Call any JD API endpoint not wrapped above (e.g. premium accounts, captcha, reconnect, speed-limit). path like '/downloadsV2/setPriority'; params is the positional argument list that endpoint expects. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool targets a distinct operation or stage (linkgrabber vs downloads vs global controller). The only adjacent tools, force_start and control_downloads, have clearly different scopes (specific items vs global state).
Most tools follow a consistent verb_noun pattern (add_links, list_downloads, set_priority). Minor deviations: status, wait_for, remove, and reset are shorter but still intuitive; no mixing of styles.
At 17 tools, the set is on the heavier side but each tool covers a meaningful function in the download lifecycle. The count is reasonable for a full-featured download manager.
The toolkit covers the full workflow: adding, collecting, moving, controlling, prioritizing, configuring directories/extraction, and removing/resetting. The raw_action fallback ensures no endpoint is unreachable, making the surface effectively complete.