Skip to main content
Glama
enesjakozh
pskill9

Website Downloader

by pskill9
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Website Downloader MCP Server

This MCP server provides a tool to download entire websites using wget. It preserves the website structure and converts links to work locally.

Prerequisites

The server requires wget to be installed on your system.

Installing wget

macOS

Using Homebrew:

brew install wget

Linux (Debian/Ubuntu)

sudo apt-get update
sudo apt-get install wget

Linux (Red Hat/Fedora)

sudo dnf install wget

Windows

  1. Using Chocolatey:

choco install wget

  1. Or download the binary from: https://eternallybored.org/misc/wget/

    • Download the latest wget.exe

    • Place it in a directory that's in your PATH (e.g., C:\Windows\System32)

Related MCP server: MCP Windows Website Downloader Server

Usage

The server provides a tool called download_website with the following parameters:

  • url (required): The URL of the website to download

  • outputPath (optional): The directory where the website should be downloaded. Defaults to the current directory.

  • depth (optional): Maximum depth level for recursive downloading. Defaults to infinite. Set to 0 for just the specified page, 1 for direct links, etc.

Example

{
  "url": "https://example.com",
  "outputPath": "/path/to/output",
  "depth": 2  // Optional: Download up to 2 levels deep
}

Features

The website downloader:

  • Downloads recursively with infinite depth

  • Includes all page requisites (CSS, images, etc.)

  • Converts links to work locally

  • Adds appropriate extensions to files

  • Restricts downloads to the same domain

  • Preserves the website structure

Installation

  1. Build the server:

npm install
npm run build

  1. Add to MCP settings:

{
  "mcpServers": {
    "website-downloader": {
      "command": "node",
      "args": ["/path/to/website-downloader/build/index.js"]
    }
  }
}

Available Tools

1 tool
download_websiteC

Download an entire website using wget

ParametersJSON Schema
NameRequiredDescriptionDefault
depthNoMaximum depth level for recursive downloading (optional, defaults to infinite)
outputPathNoPath where the website should be downloaded (optional, defaults to current directory)
urlYesURL of the website to download

TDQS

C2.9/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 using wget, which implies network operations and file system writes, but doesn't specify potential side effects like data consumption, rate limits, or file overwriting risks. This leaves significant gaps in understanding the tool's behavior.

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 any unnecessary words. It is front-loaded and appropriately sized, making it easy to understand quickly.

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?

Given the tool's complexity (downloading entire websites with potential network and file system impacts), no annotations, and no output schema, the description is insufficient. It lacks details on return values, error handling, or operational constraints, leaving the agent with incomplete information for safe and effective use.

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 already documents all parameters thoroughly. The description adds no additional meaning or context beyond what the schema provides, such as explaining how depth affects recursion or outputPath usage. Thus, it meets the baseline for high schema coverage without adding value.

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 ('an entire website'), specifying the method ('using wget'). It distinguishes the tool's scope as downloading entire websites, which is specific. However, without sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.

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 or any context for its application. It lacks information about prerequisites, such as internet connectivity or permissions, and doesn't mention any exclusions or best practices for usage.

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. 1 tool updatev1.0.0
    • First observeddownload_website
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as downloading websites, leaving no room for confusion or misselection.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (download_website), which is consistent and predictable. Since there are no other tools to compare against, the naming is inherently consistent.

Tool Count2/5

A single tool is too few for a server named 'Website Downloader', as it suggests a limited scope that may not cover related operations like checking download status, managing downloads, or handling errors. This minimal set feels thin and incomplete for the domain.

Completeness2/5

The tool surface is severely incomplete for website downloading. While download_website handles the core action, there are obvious gaps such as listing downloads, pausing/resuming, verifying downloads, or handling configurations, which could lead to agent failures in real-world scenarios.

Maintenance

ActivityInactive
ResponsivenessSyncing

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/pskill9/website-downloader'

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