CrawlEyes MCP Server
io.github.waiky-githubPublished by GitHub account waiky-githubv0.2.0Updated Oct 24, 2026
Web scraping & search for AI agents: extract, SearXNG search, rerank, robots compliance. No API key.
Overview
CrawlEyes gives an assistant web search, full-text page extraction, sitemap discovery, and cited deep-research reports through a local MCP server.
- What you can do
- Exposes four MCP tools: search (SearXNG first, with a keyless Tavily fallback and optional local semantic reranking), extract (headless-browser scraping to Markdown, denoised, raw, or citation formats), deep_research (decomposes a topic, searches, extracts, and synthesizes a cited report), and sitemap (URL discovery from sitemap.xml with robots.txt fallback). It also offers a Firecrawl-compatible /scrape endpoint and RAG-ready helpers. Extracted content is sanitized against prompt injection, and tools share rate limiting and backoff.
- When to use it
- Use it when an assistant needs to read web pages, run searches, or assemble cited research without paid search accounts, including on networks where common search APIs are blocked. It suits local desktop MCP clients that can run a Python process.
- Requirements
- Runs locally over stdio (or streamable-http) as the PyPI package crawleyes, needing Python 3.12, Crawl4AI, and a Playwright Chromium browser. Optional SEARXNG_URL points at a self-hosted SearXNG instance; optional TAVILY_API_KEY raises search rate limits. The rerank model downloads from Hugging Face and may need a mirror endpoint.
Installation
In SourceWeft
- Open CrawlEyes MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CrawlEyes — Web Scraping & Search Toolkit for AI Agents
English | 中文
[GitHub stars] [GitHub license] [Python] [MCP] [MIT]
CrawlEyes gives AI agents reliable full-text extraction (web_extract) and robust search (web_search) backends — the "eyes" that let agents see and read the web. Built and tested against Hermes Agent.
Also ships as a standard MCP server, so any MCP client (Claude Desktop, Cursor, other agents) can reuse the same search + extraction capabilities.
Why CrawlEyes?
Most agent toolkits cover one slice of the pipeline. CrawlEyes is the rare all-in-one that you can actually run behind the Great Firewall without external accounts.
Zero API keys. Zero external accounts. One command. CrawlEyes is the only toolkit in this space that combines search + extraction + semantic reranking + MCP in a single, China-friendly, self-hosted package.
Features
Project layout
Quick start
1. Install Crawl4AI (China-friendly mirrors)
2. Scrape a page
3. Use the search + rerank (standalone, no Hermes)
China-network note: the embedding model downloads from HuggingFace, which is blocked on mainland networks. Set
HF_ENDPOINT=https://hf-mirror.comandHF_HUB_DISABLE_XET=1(hf-mirror doesn't support the xet protocol and returns 401 without this).
4. Run as an MCP server (any client)
For Hermes specifically, add to config.yaml:
4b. Firecrawl-compatible /scrape endpoint
Already using Firecrawl's Python SDK? Point it at CrawlEyes and keep your code:
This is a pragmatic subset of the Firecrawl API — the core /scrape contract
(success + data.markdown + data.metadata), backed by CrawlEyes' own
extraction engine. It does not implement Firecrawl's async /crawl queue,
/search, or /map — see the design notes for the rationale.
5. Install the search plugin (Hermes)
Copy plugins/searxng-tavily/ into a Hermes plugins dir, then:
Set SEARXNG_URL in your Hermes profile .env to point at your SearXNG instance. If unset or unreachable, the provider automatically falls back to the Tavily keyless API (no API key required).
Note: the plugin only takes effect for newly started agent sessions.
6. Verify
Design notes
- Layered composition: no single tool covers everything. Crawl4AI handles extraction; SearXNG + Tavily cover search; each layer has a tested fallback.
- Tavily keyless works with zero configuration and no account — a cheap resilience net for the whole search path.
- Circuit breaker is SearXNG-only: a Tavily fallback success does not reset the breaker (otherwise it would never trip).
record_success()is only called when SearXNG itself succeeds. - Shared SQLite cache lives in the real user home (via
pwd.getpwuid, not$HOME— which Hermes profiles override), so all profiles share one cache. WAL + 5s timeout + try/except degrade-to-no-cache under concurrency. - Semantic rerank is cheap: fastembed (ONNX) avoids the ~2GB torch dependency; model loads in ~0.6s once cached, embeddings in ~50ms.
- MCP server is standalone: it does not import Hermes internals, so it runs on any Python 3.12 env and serves any MCP client.
- MCP transport is dual: stdio (default, standard MCP clients) or
streamable-http(--transport http), so a single codebase serves both local process and remote HTTP clients. - Unified rate limiting is layered: MCP tools and deep-research's internal search/extract all share one sliding-window limiter (per-tool cost), so concurrent agent fan-out can't hammer SearXNG/Tavily/Crawl4AI even through multi-round deep research.
Credits & inspiration
This project builds on a set of excellent open-source tools. All code here is an independent implementation (no copied code), but the ideas and interfaces are drawn from the following projects — full credit to their authors:
Design independence: the implementations here are written from scratch — we studied the above projects' approaches (denoising thresholds, rerank pipelines, backoff strategies, MCP tool patterns) but did not copy their source code. Dependencies are declared in
requirements.txt. If you believe any attribution is missing or incorrect, please open an issue.
Compliance
CrawlEyes is a general-purpose fetch toolkit for legitimate research and personal use. It deliberately does not include proxy pools, fingerprint rotation, or CAPTCHA-solving (anti-scraping evasion) — those are out of scope.
Robots.txt is opt-in (default off): pass respect_robots=True to extract / markdown (or --respect-robots on the CLI) to check each target's robots.txt (RFC 9309) and refuse URLs it explicitly disallows. It's default-off so legitimate scraping isn't silently blocked by aggressive or broken robots rules — compliance is the caller's informed choice per use case. Always review each site's terms of service before scraping at scale.
License
MIT — see LICENSE.
📮 关注我们
公众号:AI Aperture —— 分享 AI 工程实践、多 Agent 系统与开源项目经验。
扫码关注,获取项目更新与更多技术内容。
Source: README.md at commit f20a7a7
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts