Skip to main content
Glama
dmitryglhf

url-download-mcp

by dmitryglhf
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

MCP URL Downloader

A Model Context Protocol (MCP) server that enables AI assistants to download files from URLs to the local filesystem.

Features

  • Download single or multiple files from URLs with concurrent support

  • File size validation (configurable, default 500MB)

  • Unique filename generation to prevent overwrites

  • Security

Related MCP server: Website Downloader

Installation

# Using uvx (recommended)
uvx mcp-url-downloader

# Using pip
pip install mcp-url-downloader

# From source
git clone https://github.com/dmitryglhf/mcp-url-downloader.git
cd mcp-url-downloader
uv sync

Configuration

Claude Desktop

To integrate server with Claude, add the following to your claude_desktop_config.json file:

{
  "mcpServers": {
    "url-downloader": {
      "command": "uvx",
      "args": ["mcp-url-downloader"]
    }
  }
}

Tools

download_single_file

Download a single file from a URL with optional custom filename.

Parameters:

  • url (string, required): URL of the file to download

    • Must be a valid HTTP/HTTPS URL

    • Maximum length: 2048 characters

  • output_dir (string, optional): Directory to save the file

    • Default: ~/Downloads/mcp-downloads/

    • Must be a valid writable directory path

  • filename (string, optional): Custom filename for the saved file

    • If not provided, extracted from URL

    • Will be sanitized automatically

    • Extension will be preserved or detected

  • timeout (number, optional): Download timeout in seconds

    • Default: 60

    • Range: 1-300

  • max_size_mb (number, optional): Maximum file size in MB

    • Default: 500

    • Range: 1-5000

download_files

Download multiple files from URLs concurrently.

Parameters:

  • urls (array of strings, required): List of URLs to download

    • Each URL must be valid HTTP/HTTPS

    • Maximum: 100 URLs per request

    • Each URL max length: 2048 characters

  • output_dir (string, optional): Directory to save all files

    • Default: ~/Downloads/mcp-downloads/

    • All files will be saved to this directory

  • timeout (number, optional): Download timeout in seconds per file

    • Default: 60

    • Range: 1-300

  • max_size_mb (number, optional): Maximum file size in MB per file

    • Default: 500

    • Range: 1-5000

Rate Limits

  • Maximum 100 URLs per download_files request

  • Maximum concurrent downloads: 10 (configurable up to 50)

  • URL length limited to 2048 characters

  • Timeout range: 1-300 seconds

  • File size range: 1-5000 MB

Development

# Run tests
uv run pytest

Available Tools

2 tools
download_filesB

Download multiple files from URLs and save to local filesystem.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlsYesList of URLs to download
output_dirNoDirectory to save downloaded files
timeoutNoDownload timeout in seconds
max_size_mbNoMaximum file size in MB (default: 500)

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultsYesList of download results
failed_countYesNumber of failed downloads
success_countYesNumber of successful downloads

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions saving to the local filesystem, which implies a write operation, but lacks details on permissions, error handling, rate limits, or what happens if files already exist. For a tool with no annotations and potential side effects, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which handles return values) and full schema coverage for parameters, the description's minimalism is partially acceptable. However, for a tool that performs downloads and file system writes with no annotations, more context on behavior and usage would improve completeness, leaving it at an adequate but basic level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond what's in the schema, such as explaining parameter interactions or providing examples. Baseline 3 is appropriate when the schema handles all parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('download multiple files') and resource ('from URLs'), and distinguishes from the sibling tool 'download_single_file' by specifying 'multiple files'. However, it doesn't explicitly mention the sibling tool name or contrast their purposes directly, keeping it at a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'download_single_file', nor does it mention any prerequisites, constraints, or typical use cases. It states what the tool does but not when it's appropriate, resulting in minimal usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

download_single_fileC

Download a single file from URL with optional custom filename.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the file to download
output_dirNoDirectory to save the file
filenameNoCustom filename (optional)
timeoutNoDownload timeout in seconds
max_size_mbNoMaximum file size in MB (default: 500)

Output Schema

ParametersJSON Schema
NameRequiredDescription
errorNoError message if download failed
successYesWhether the download was successful
file_nameYesName of the downloaded file
file_pathYesFull path where the file was saved
file_sizeYesSize of the downloaded file in bytes
content_typeNoMIME type of the downloaded file

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only mentions optional filename customization. It fails to disclose critical behavioral traits like network dependencies, file system interactions, timeout behavior, size limits, error handling, or output location details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, this is a network/filesystem operation with 5 parameters and no annotations. The description is inadequate for such complexity - it doesn't address security considerations, failure modes, or what happens with the downloaded file.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds minimal value by mentioning 'optional custom filename' which corresponds to the 'filename' parameter, but doesn't provide additional context beyond what the schema already specifies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Download') and resource ('a single file from URL'), distinguishing it from the sibling tool 'download_files' which suggests batch operations. However, it doesn't explicitly contrast with the sibling beyond the 'single' qualifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus 'download_files' or other alternatives. It mentions 'optional custom filename' but gives no context about prerequisites, error conditions, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • Changeddownload_files1 field changed
      • addedInput schema / title
        Added value: +"download_filesArguments"
    • Changeddownload_single_file1 field changed
      • addedInput schema / title
        Added value: +"download_single_fileArguments"
  2. 2 tool updates
    • First observeddownload_files
    • First observeddownload_single_file
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation3/5

The two tools have overlapping purposes—both download files from URLs—but their descriptions help differentiate them: one handles multiple files, the other a single file with optional custom naming. However, the core functionality is similar, which could lead to confusion about when to use each.

Naming Consistency5/5

The tool names follow a consistent verb_noun pattern with snake_case throughout: 'download_files' and 'download_single_file'. Both start with 'download' and clearly describe their scope, making the naming predictable and easy to understand.

Tool Count3/5

With only 2 tools, the server feels thin for a URL download domain, as it lacks operations like checking download status, handling errors, or managing downloads. While the tools cover basic downloading, the count is borderline for providing a complete surface.

Completeness2/5

The tool set is significantly incomplete for a URL download server. It lacks essential operations such as validating URLs, pausing/resuming downloads, handling authentication, or providing progress updates. This will likely cause agent failures in more complex scenarios.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

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/dmitryglhf/url-download-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server