Which scraping MCP server to use: pick by the job

"Which scraping MCP server should I use?" has no answer until you say what the agent is supposed to do. A browser server, a crawl platform, a self-hosted crawler and a single-page content API are four different tools. They overlap at the edges, but each one is the right fit for a different job and an expensive fit for the others. This guide starts from the job.

Six common jobs

1. A coding agent reads documentation. Claude Code or Cursor needs one library page, a changelog or an API reference as text while it writes code. The URLs are known or easy to guess.
2. An agent answers questions from a few public pages. A support or research agent pulls three to ten known public pages into context and cites them.
3. An agent steps through a flow. It clicks, types and waits: testing your own web app, reproducing a bug, filling a form in a staging environment.
4. A team maps a whole public docs site. It needs every page under a path, not one page at a time.
5. Data must stay on your own machines. Policy says no third-party service sees the URLs or the content.
6. Somebody wants pages from a specific named website at scale. This one is out of scope here; check the site's terms and API first, and read the responsible scraping guide.

Decision table

The full rows for each server are in the rubric guide.

Choose it when, skip it when

Single-page content API

Choose it when the agent reads known public URLs and you care about context size. These servers return the main content of one page as Markdown or text, usually with a size cap. Jina's server lets you filter its 12 tools down in the URL; Live Web Data API's exposes two. The output and token cost guide shows how much context each choice saves.

Skip it when the page only shows content after JavaScript runs and your chosen API does not render it, or when the job needs clicks, crawling or search. Live Web Data API, for example, does not render JavaScript, crawl, search or extract structured fields.

Browser-control server

Choose it when the job is interaction. Playwright MCP drives a real browser through the page's accessibility tree, which is exactly right for form flows and UI testing.

Skip it when the job is reading. About 25 tools, a browser process and a snapshot after each step are a heavy way to fetch a docs page. It is the mismatch to check for first.

Crawl platform

Choose it when you need many pages from one site: a map of URLs, a crawl with a status check, or batch scraping. Firecrawl and Apify both offer hosted MCP endpoints for this. Already on Firecrawl and unhappy with the fit? The Firecrawl MCP alternatives guide sorts the options by your reason to switch.

Skip it when you only ever read a handful of known URLs. In a client that loads tools upfront, a large tool surface then costs context in every session for features the agent never calls, unless you narrow it.

Self-hosted crawler

Choose it when URLs and content must not leave your infrastructure, or you want to change the code. Crawl4AI's Docker server exposes MCP over SSE and WebSocket; Scrapling and Playwright MCP run locally.

Skip it when nobody on the team wants to own updates, browser versions, memory limits and the request-rate policy of the machine it runs on.

Setting up the server you picked

This site compares servers; it does not walk through client configuration. For step-by-step setup in Claude Code, Cursor and other clients, the remote MCP server setup guide on fetchmcp.net covers each one. Once a server is connected, run the test from the rubric: one known page and one known 404 on example.com, then compare the output size and the error text.

If a content API fits

Live Web Data API is one of the content APIs in the decision table. Its MCP server does not render JavaScript, crawl, search or extract structured fields. If reading known public pages is your job, read the MCP docs. Sign-up is for businesses only. Only Business, Enterprise and Custom sign-ups are reviewed before checkout, usually within 1 business day.