abdm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ABDM_PORT | No | Port of the ABDM local integration server (auto-discovered from appSettings.json). | 15151 |
| ABDM_API_KEY | No | Optional authentication key configured in ABDM. | |
| ABDM_CLI_PATH | No | Explicit path to ABDownloadManagerCli executable. | Auto-detected |
| ABDM_CONFIG_DIR | No | Custom or portable configuration directory path. | ~/.abdm |
| ABDM_MCP_DEFAULT_MODE | No | Default mode: interactive (GUI confirmation) or headless (silent background). | interactive |
| ABDM_MCP_MAX_BATCH_SIZE | No | Maximum URLs accepted in a single abdm_download_batch call. | 50 |
| ABDM_MCP_ALLOW_FILE_DELETION | No | Set to true to permit abdm_remove(delete_file=True). | false |
| ABDM_MCP_ALLOWED_DOWNLOAD_ROOTS | No | Comma-separated list of allowed download directories. | ~/Downloads/ABDM |
| ABDM_MCP_ALLOW_PRIVATE_NETWORKS | No | Set to true to allow downloads from LAN / private IPs. | false |
| ABDM_MCP_ALLOW_SENSITIVE_HEADERS | No | Set to true to allow Cookie and Authorization headers. | false |
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 |
|---|---|
| abdm_downloadA | Submit an HTTP/HTTPS download task to AB Download Manager with multi-threaded acceleration. In 'interactive' mode, triggers the desktop confirmation GUI. In 'headless' mode, starts silent background download into allowed sandboxed folder. |
| abdm_download_hlsA | Download an HLS (.m3u8) streaming video/audio task with segment reassembly. In 'interactive' mode, triggers the desktop confirmation GUI. In 'headless' mode, starts silent background download into allowed sandboxed folder. |
| abdm_download_batchA | Enqueue up to 50 URLs in a batch with per-item status tracking. |
| abdm_get_queuesA | List all configured download queues in AB Download Manager. |
| abdm_check_statusA | Inspect reachability, authentication, port discovery, and capabilities. |
| abdm_list_downloadsB | List downloads currently tracked by AB Download Manager. |
| abdm_get_downloadA | Fetch detailed metadata for a single download task by ID. |
| abdm_pauseA | Pause one or more active download tasks by ID. |
| abdm_resumeA | Resume one or more paused download tasks by ID. |
| abdm_pause_allA | Pause all currently active download tasks across AB Download Manager. |
| abdm_resume_allA | Resume all currently paused download tasks across AB Download Manager. |
| abdm_removeA | Remove/cancel one or more download tasks. File deletion requires explicit policy opt-in (ABDM_MCP_ALLOW_FILE_DELETION=true) and path verification. |
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 12 tools
Each tool targets a distinct action or resource: download submission (HTTP, HLS, batch), task inspection, lifecycle controls (pause/resume/remove), and server status. Single vs. all pause/resume variants are clearly separated by the '_all' suffix.
All tools share the 'abdm_' prefix and use snake_case, with mostly clear verb_noun naming. Minor deviations: 'abdm_download' and 'abdm_pause' omit explicit objects while related batch/all variants include suffixes.
12 tools is well-scoped for a download manager MCP server, covering submission, listing, status, and lifecycle actions without unnecessary surface area. Every tool corresponds to a meaningful operation.
The download task lifecycle is well covered: create via download/HLS/batch, read via list/get, pause/resume/remove. Queue support is read-only (only get_queues) and there is no explicit update/options editing, which is a minor gap.