MCP Website Downloader

Created By
angrysky56a year ago
MCP tool for Claude to download entire Windows working website url and assets and save to a library for AI use.
Overview

what is MCP Website Downloader?

MCP Website Downloader is a tool designed to download entire Windows-based documentation websites and their assets, organizing them for AI use.

how to use MCP Website Downloader?

To use the MCP Website Downloader, fork the repository, set up a virtual environment, and configure the tool in your claude_desktop_config.json. You can then start the server and use it through Claude Desktop or other MCP clients to download websites.

key features of MCP Website Downloader?

  • Downloads complete documentation sites and organizes assets (CSS, JS, images).
  • Maintains a clean index for RAG systems.
  • Simple single-purpose MCP interface for easy usage.

use cases of MCP Website Downloader?

  1. Downloading and archiving documentation for offline access.
  2. Preparing documentation sites for RAG indexing.
  3. Organizing web assets for AI processing.

FAQ from MCP Website Downloader?

  • Can MCP Website Downloader handle all types of websites?

It is primarily designed for documentation websites and may not work optimally with all site types.

  • Is there a limit to the size of the website that can be downloaded?

The tool has reasonable depth limits to prevent excessive recursion and ensure efficient downloads.

  • What happens if there is an error during the download?

The server has error handling for common issues like invalid URLs and network errors, providing detailed error messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
angrysky56
Star
4
Language
Python
License
MIT license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago