Anycrawl MCP Server

Anycrawl MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. AnyCrawl MCP Server, with Scrape, Crawl and SERP.

What you get

🚀 AnyCrawl MCP Server — Powerful web scraping and crawling for Cursor, Claude, and other LLM clients via the Model Context Protocol (MCP).

AnyCrawl is a powerful Node.js/TypeScript crawler that turns websites into LLM-ready data and extracts structured SERP results from Google/Bing/Baidu/etc. It features native multi-threading for bulk processing and supports multiple output formats.

• Web Scraping — Extract content from single URLs with multiple output formats
• Website Crawling — Crawl entire websites with configurable depth and limits
• Search Engine Integration — Search the web and optionally scrape results
• Multiple Engines — Auto mode (intelligent selection), Playwright, Cheerio, and Puppeteer
• Flexible Output — Markdown, HTML, text, screenshots, and structured JSON
• Async Operations — Non-blocking crawl jobs with status monitoring

What the assistant can call

Once Anycrawl is connected, these are the calls the assistant has available:

• SSE — https://mcp.anycrawl.dev/{API_KEY}/sse
• Markdown — Clean, structured markdown content perfect for LLM consumption
• HTML — The HTML tool exposed by this server
• Text — The Text tool exposed by this server
• Screenshot — The Screenshot tool exposed by this server
• Cheerio — The Cheerio tool exposed by this server
• Playwright — The Playwright tool exposed by this server
• Puppeteer — The Puppeteer tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server
• Build — The Build tool exposed by this server
• Test — The Test tool exposed by this server

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 6 environment variables: ANYCRAWL_API_KEY, ANYCRAWL_BASE_URL, ANYCRAWL_HOST, ANYCRAWL_PORT, LOG_LEVEL, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ - npm

Choosing this one

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Anycrawl's toolset — SSE, Markdown, HTML and 11 more — is a fair guide to whether it matches your workflow. It is maintained by any4ai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Anycrawl.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the anycrawl mcp server does with a few real requests.