Mcp Web Reader

Created By
zacfirea year ago
让Claude等大语言模型轻松获取和解析任何网页内容,并转化为干净的Markdown。支持双引擎、批量处理,增强AI互联网信息处理能力。
Overview

what is Mcp Web Reader?

Mcp Web Reader is a powerful server that enables large language models like Claude to read and parse web content, converting it into clean Markdown format.

how to use Mcp Web Reader?

To use Mcp Web Reader, configure it in the Claude Desktop application and use specific commands to fetch web content either individually or in bulk.

key features of Mcp Web Reader?

  • 🚀 Dual Engine Support: Integrates Jina Reader API and local parser.
  • 🔄 Smart Downgrade: Automatically switches to local parsing if Jina Reader fails.
  • 📦 Batch Processing: Supports fetching multiple URLs simultaneously.
  • 🎯 Flexible Control: Allows forcing the use of a specific parsing method.
  • 📝 Markdown Output: Automatically converts content to clear Markdown format.

use cases of Mcp Web Reader?

  1. Extracting content from various web pages for analysis.
  2. Converting web articles into Markdown for documentation.
  3. Enabling AI models to process and understand web content efficiently.

FAQ from Mcp Web Reader?

  • Can Mcp Web Reader handle multiple URLs at once?

Yes! It supports batch processing for multiple URLs.

  • Is there a way to force a specific parsing method?

Yes! You can choose to force either the Jina Reader or the local parser.

  • What output format does Mcp Web Reader provide?

It converts the fetched content into clean Markdown format.

Server Config

{
  "mcpServers": {
    "web-reader": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-web-reader/dist/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zacfire
Star
-
Language
-
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
Crevio

2 days ago