redup.mcp-web-parser

redup.mcp-web-parser

MCP server that parses web pages into clean markdown via Crawl4AI's HTTP API, exposing parse_page and health-check tools with configurable proxy and timeout.

Category
Visit Server

README

redup.mcp-web-parser

Docker test Python test

MCP Streamable HTTP service that parses web pages into cleaned markdown via Crawl4AI POST /crawl (0.8.x).

Model

  • Thin MCP façade over Crawl4AI HTTP API — no browser in this image.
  • Crawl requests set exclude_all_images (and disable screenshot/pdf) so upstream payloads stay small; markdown and links are unchanged for tools.
  • upstream_base_url is required at runtime (config or McpWebParser___upstream_base_url). Defaults ship empty (OSS-safe: no cluster hostnames or internal proxies in the repo).
  • Optional egress proxy for Crawl4AI IP substitution via server config default_proxycrawler_config.proxy_config.server. Empty = direct fetch. Proxy is not a tool argument (deploy/runtime only).
  • Tool results are JSON (success / markdown / status_code / …), not a concatenated text dump.
  • Targeted at Crawl4AI 0.8.x (per-request proxy_config works). On 0.9+ Docker API may reject proxy / proxy_config in the request body.

Contract: MCP tools parse_page, fetch_binary. Endpoint: POST http://<host>:8000/mcp (stateless Streamable HTTP, JSON). Metrics: GET http://<host>:9999/metrics (Prometheus via redup-servicekit).

Tool args:

  • parse_page — HTML pages → markdown JSON. Not for PDF/DOCX/ZIP/images (is_binary=true → switch to fetch_binary).
  • fetch_binary — download binary files (pdf/docx/zip/images/…). Download only (no OCR/unzip). Bytes only in JSON content_base64 (no shared disk path). Downstream tools must accept those bytes via their own input contract. Not a fallback when HTML parse_page fails.

Agent registration example: {"id":"web-parser","url":"http://…:8000/mcp"} → LLM names mcp__web-parser__parse_page / mcp__web-parser__fetch_binary.

Configuration

config/config.yaml:

service:
  console_log_level: INFO
  host: "0.0.0.0"
  port: 8000
  path: /mcp
  max_workers: 4
  hpa_max_workers: 2

McpWebParser:
  upstream_base_url: ""
  upstream_token: ""
  default_proxy: ""
  request_timeout_seconds: 120
  max_timeout_seconds: 300
  max_markdown_chars: 100000
  max_binary_bytes: 15728640
  delay_before_return_html: 2.5
  json_response: true
  stateless_http: true

Override via servicekit env substitution (section___key):

export McpWebParser___upstream_base_url=https://crawl4ai.example.com
export McpWebParser___default_proxy=http://user:pass@proxy.example:3128
export McpWebParser___upstream_token=
export service___port=8000

Startup fails fast if upstream_base_url is empty.

Run with Docker

docker run --rm -p 8000:8000 -p 9999:9999 \
  -e McpWebParser___upstream_base_url=https://crawl4ai.example.com \
  -e McpWebParser___default_proxy=http://proxy.example:3128 \
  redup4ai/redup.mcp-web-parser:0.1.0-3.13-slim

MCP URL: http://127.0.0.1:8000/mcp. Metrics: http://127.0.0.1:9999/metrics.

GitHub Release publishes {VERSION}-3.13-slim to Docker Hub (DOCKERHUB_USER / DOCKERHUB_PASSWORD secrets).

Run locally without Docker

Requires Python 3.13+ and a reachable Crawl4AI base URL:

export McpWebParser___upstream_base_url=https://crawl4ai.example.com
uv sync
uv run python -m redup_mcp_web_parser.service config/config.yaml

Desktop MCP clients (stdio):

uv run redup-mcp-web-parser \
  --transport stdio \
  --upstream-base-url https://crawl4ai.example.com

Tests

uv sync --dev
uv run pytest tests -q -m "not live"

Optional live smoke (needs a real Crawl4AI):

export McpWebParser___upstream_base_url=https://crawl4ai.example.com
uv run pytest tests -m live -q

License

MIT — see LICENSE and NOTICE.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
E2B

E2B

Using MCP to run code via e2b.

Official
Featured