mcpField
S
Scraperapi

Scraperapi

Remote
pipeworx.ioBrowser Automation0Updated 5w ago

About Scraperapi

Scraperapi provides MCP tools for web-page scraping, Amazon product and search data, and Google search results. It is for users who need page content or structured results, with options for JavaScript rendering and location targeting.

Key features

  1. 01Scrape pages as HTML or Markdown
  2. 02Render JavaScript-heavy pages
  3. 03Retrieve Amazon product details by ASIN
  4. 04Search Amazon and Google with structured results

Use cases

  1. 01Collect page content for analysis
  2. 02Scrape a JavaScript-driven site
  3. 03Look up Amazon product details or listings
  4. 04Retrieve Google search results for a query

MCP support

Exposes ScraperAPI scraping and search tools to MCP clients. It can connect through Pipeworx or run as a standalone local stdio MCP server; calls require the user's ScraperAPI key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/scraperapi/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-scraperapi

ScraperAPI MCP — wraps ScraperAPI (scraperapi.com), a proxy-based web

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
scraperapi_scrapeScrape any web page through ScraperAPI's rotating proxies and return its content. Returns HTML by default, or clean markdown with output_format:"markdown" (ideal for feeding an LLM). Use render:true for JavaScript-heavy pages (SPAs), premium:true for hard-to-scrape sites (residential proxies), and country_code to geotarget. Example: scraperapi_scrape({ url: "https://example.com", output_format: "markdown", render: true, _apiKey: "your-key" })
scraperapi_amazon_productGet structured Amazon product data by ASIN — title, price, rating, reviews count, features, images, availability. Example: scraperapi_amazon_product({ asin: "B0BFC7WQ6R", country: "us", tld: "com", _apiKey: "your-key" })
scraperapi_amazon_searchSearch Amazon and get structured results — product titles, ASINs, prices, ratings, thumbnails. Example: scraperapi_amazon_search({ query: "wireless earbuds", country: "us", tld: "com", _apiKey: "your-key" })
scraperapi_google_searchRun a Google search and get structured SERP results — organic results, titles, links, snippets, and related data. Example: scraperapi_google_search({ query: "best running shoes 2026", country_code: "us", tld: "com", _apiKey: "your-key" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "scraperapi": {
      "url": "https://gateway.pipeworx.io/scraperapi/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/scraperapi/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/scraperapi_scrape. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "scraperapi": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-scraperapi"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-scraperapi

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Scraperapi data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.