mcp-scraperapi
Provides tools for retrieving structured Amazon product data by ASIN and searching Amazon, returning product titles, prices, ratings, review counts, features, images, and availability.
Provides a tool for running Google searches and retrieving structured search engine results, including organic results, titles, links, snippets, and related data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-scraperapiScrape https://example.com and return it as markdown"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-scraperapi
ScraperAPI MCP — wraps ScraperAPI (scraperapi.com), a proxy-based web
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
Tool | Description |
| Scrape 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" }) |
| Get 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" }) |
| Search 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" }) |
| Run 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" }) |
Related MCP server: Thordata MCP Server
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 1576+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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-scraperapiIt 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
This server cannot be deployed
Maintenance
Related MCP Connectors
Cloud scraping & crawling API for AI agents. Turn any URL into clean, LLM-ready markdown.
Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.
Turn any URL into clean Markdown and structured data. Scrape, crawl, search and extract.
Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables web scraping and document processing with JavaScript execution, anti-detection measures, batch processing, and structured data extraction. Supports multiple formats including markdown, HTML, screenshots, and handles PDFs with OCR capabilities.4MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI models to scrape and extract structured data from any website globally using a 195+ country proxy network with JavaScript rendering, anti-bot bypass, and output in Markdown, HTML, or Links format.MIT
- AlicenseBqualityBmaintenanceEnables web scraping and data extraction from websites with geographic flexibility, privacy features, and anti-detection capabilities. Supports scraping general websites, Google Search, Amazon Search, and Reddit with customizable parameters for rendering, geolocation, and locale.30105 npm37ISC
- AlicenseAqualityDmaintenanceEnables web scraping of URLs, including extracting text, links, images, metadata, taking screenshots, and using CSS selectors for structured data extraction.68 npmMIT