Site Cloner MCP Server

Created By
SarthakMishraa year ago
MCP server to help LLMs clone websites by providing tools to fetch, analyze, and download website assets.
Overview

What is Site Cloner MCP Server?

Site Cloner MCP Server is a Model Context Protocol (MCP) server designed to assist Large Language Models (LLMs) in cloning websites by providing tools to fetch, analyze, and download website assets.

How to use Site Cloner MCP Server?

To use the Site Cloner MCP Server, you need to have Docker installed. Build the Docker image and run the container. You can also configure it in Cursor for easier access.

Key features of Site Cloner MCP Server?

  • Fetch HTML content from any URL
  • Extract assets (CSS, JavaScript, images, fonts, etc.) from HTML content
  • Download individual assets to a local directory
  • Parse CSS files to extract linked assets
  • Create a sitemap of a website
  • Analyze page structure and layout

Use cases of Site Cloner MCP Server?

  1. Cloning websites for offline access
  2. Analyzing website structures for research
  3. Extracting assets for web development projects

FAQ from Site Cloner MCP Server?

  • Can I clone any website?

Yes, but be mindful of copyright and terms of service restrictions.

  • Do I need to install anything besides Docker?

No, Docker is the only requirement to run the server.

  • What if the server doesn't show up in Cursor?

Restart Cursor, check your configuration file, and ensure Docker is running.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago