Schema | mcp-curl-downloader

mcp-curl-downloader

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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": true }

Tools

Functions exposed to the LLM to take actions

Name	Description
download_fileA	Download a file from a URL to a local directory or file path. Features: Supports HTTP and HTTPS protocols Streams large files efficiently (no memory pressure) Auto-detects filename from URL or Content-Disposition header Creates parent directories automatically Configurable timeout (300s) and size limit (500MB) Safe filename sanitization (removes dangerous characters) Examples: Download to directory: { "url": "https://example.com/file.pdf", "dest_path": "/home/user/downloads" } Download with custom name: { "url": "https://example.com/data.csv", "dest_path": "/tmp", "filename": "my_data.csv" } With auth headers: { "url": "https://api.example.com/export", "dest_path": "./output.json", "headers": { "Authorization": "Bearer token123" } }

Name

Description

download_fileA

Download a file from a URL to a local directory or file path.

Features:

Supports HTTP and HTTPS protocols
Streams large files efficiently (no memory pressure)
Auto-detects filename from URL or Content-Disposition header
Creates parent directories automatically
Configurable timeout (300s) and size limit (500MB)
Safe filename sanitization (removes dangerous characters)

Examples:

Download to directory: { "url": "https://example.com/file.pdf", "dest_path": "/home/user/downloads" }
Download with custom name: { "url": "https://example.com/data.csv", "dest_path": "/tmp", "filename": "my_data.csv" }
With auth headers: { "url": "https://api.example.com/export", "dest_path": "./output.json", "headers": { "Authorization": "Bearer token123" } }

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored 2026-08-04 02:15 across 1 tool

Disambiguation5/5

There is only one tool, so there is zero ambiguity between tools. The tool has a single, clearly defined purpose: downloading files from a URL.

Naming Consistency3/5

With only one tool, there is no pattern to evaluate for consistency. The name 'download_file' uses a reasonable verb_noun convention, but a single tool doesn't demonstrate any naming system.

Tool Count2/5

A single tool feels thin for a downloader server. The downloader domain could reasonably include tools like list_directory, delete_file, or check_file_status to provide a more complete surface, though a minimalist download-only server is defensible.

Completeness2/5

The tool covers download functionality well, but represents a dead-end surface. There is no way to check whether a download succeeded (no status/history), no way to remove downloaded files, or resolve/validate URLs before downloading. Agents hit a hard wall after invoking download_file.

Maintenance

ActivityStale

ResponsivenessNo issues

Resources

Need Help?

Related Servers