Claude Web Scraper MCP

Created By
vishwajeetdabholkara year ago
A simple MCP server that integrates eGet web scraper with Claude for Desktop. This connector allows Claude to scrape web content through your local eGet API, enabling search, summarization, and analysis of websites directly in conversations.
Overview

what is Claude Web Scraper MCP?

Claude Web Scraper MCP is a Model Context Protocol (MCP) server that integrates the eGet web scraper with Claude for Desktop, allowing users to scrape web content through a local API.

how to use Claude Web Scraper MCP?

To use the Claude Web Scraper MCP, set up the eGet web scraper and the MCP server, then configure Claude for Desktop to connect to the MCP server. You can issue commands to scrape and summarize website content directly in Claude.

key features of Claude Web Scraper MCP?

  • Integration with eGet web scraper for web content extraction
  • Local API for scraping and summarization
  • Easy setup and configuration with Claude for Desktop

use cases of Claude Web Scraper MCP?

  1. Scraping content from news websites for summaries.
  2. Extracting data from e-commerce sites for analysis.
  3. Gathering information from various online sources for research purposes.

FAQ from Claude Web Scraper MCP?

  • What are the prerequisites for using Claude Web Scraper MCP?

You need Claude for Desktop, Python 3.7+, and the eGet web scraper.

  • How do I set up the eGet web scraper?

Follow the setup instructions provided in the documentation to clone the repository and run the scraper.

  • Can I use Claude Web Scraper MCP on Windows?

Yes, the setup instructions include steps for Windows users.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vishwajeetdabholkar
Star
2
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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