About ScrapingBee
ScrapingBee is a hosted MCP server that gives AI agents structured access to web pages, search results, and platform-specific data through the ScrapingBee API. Its tools cover page extraction, Google and marketplace searches, video data, and queries to ChatGPT or Gemini.
Key features
- 01Retrieve rendered page text, HTML, and screenshots
- 02Extract data with CSS or XPath selectors
- 03Search Google, Amazon, Walmart, and YouTube
- 04Get product, video, and file data
- 05Send prompts to ChatGPT or Gemini
- 06Check account credits and concurrency
Use cases
- 01Extract selected fields from a web page
- 02Search products and retrieve seller pricing
- 03Find YouTube videos and fetch metadata or subtitles
- 04Check remaining API credits
MCP support
The hosted server at `https://mcp.scrapingbee.com/mcp` exposes ScrapingBee capabilities as MCP tools. Clients send a ScrapingBee API key in the authorization header.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.scrapingbee.com/mcpclaude mcp add --transport http com-scrapingbee https://mcp.scrapingbee.com/mcp{"mcpServers":{"com-scrapingbee":{"type":"http","url":"https://mcp.scrapingbee.com/mcp"}}}Open in Cursor{"servers":{"com-scrapingbee":{"type":"http","url":"https://mcp.scrapingbee.com/mcp"}}}Open in VS Code{"mcpServers":{"com-scrapingbee":{"type":"http","url":"https://mcp.scrapingbee.com/mcp"}}}{"mcpServers":{"com-scrapingbee":{"serverUrl":"https://mcp.scrapingbee.com/mcp"}}}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.
https://mcp.scrapingbee.com/mcpAuth requiredTools
18| Parameter | Type | Required | Description |
|---|---|---|---|
| tag | string | No | Response-header label only. |
| pages | integer | No | The number of pages to scrape. |
| query | string | Yes | The search query to perform. |
| domain | string | No | The Amazon domain to use for the search (e.g., com, co.uk, de). |
| country | string | No | The country code for localization (e.g., us, uk, de). Do not combine with a matching domain (e.g., country=fr&domain=fr). |
| sort_by | string | No | The sort order to use for the search (most_recent, price_low_to_high, price_high_to_low, featured, average_review, bestsellers). |
| add_html | boolean | No | Whether to return the HTML along with the search results. |
| currency | string | No | The currency code (ISO 4217) to display results (e.g., USD, GBP, EUR). |
| language | string | No | The language code to display results (e.g., en, fr, de). |
| zip_code | string | No | The ZIP code to use for delivery localization. |
| screenshot | boolean | No | Force a browser screenshot (returns base64 image). |
| start_page | integer | No | The page number to start scraping from. |
| category_id | string | No | The category ID to use for the search. |
| merchant_id | string | No | The merchant ID to use for the search. |
| light_request | boolean | No | Whether to use a light request or not. |
| autoselect_variant | boolean | No | Automatically select the default/most-popular variant. |
Details
From the project READMEScrapingBee MCP Server
A production-ready Model Context Protocol (MCP) server that enables AI agents to access structured web data using ScrapingBee as a tool.
This project demonstrates how to transform ScrapingBee into an AI-native data layer. Instead of embedding scraping logic directly inside prompts, AI agents register ScrapingBee as a tool and request structured web data on demand.
If you are building:
• AI agents that require live web access
• Autonomous research systems
• Ecommerce intelligence bots
• Market monitoring agents
• LLM workflows with tool execution
• AI-powered web scraping infrastructure
This repository provides a complete MCP integration blueprint.
Quick start
The server is hosted by ScrapingBee at https://mcp.scrapingbee.com/mcp (Streamable HTTP) —
there is nothing to install. You need a ScrapingBee API key
(get one here; trial credits included),
sent as the header Authorization: Bearer <key>. Registry name: com.scrapingbee/mcp.
Claude Code
claude mcp add --transport http scrapingbee https://mcp.scrapingbee.com/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
Codex CLI
codex mcp add scrapingbee --url https://mcp.scrapingbee.com/mcp \
--bearer-token-env-var SCRAPINGBEE_API_KEY
Cursor, VS Code and other clients with a JSON config
{
"mcpServers": {
"scrapingbee": {
"url": "https://mcp.scrapingbee.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Also available through Glama, Smithery and the MCP Registry.
Tools
| Tool | What it does |
|---|---|
get_page_text | Fetch a URL and return its content as text or markdown (JavaScript rendered, blocks handled) |
get_page_html | Fetch a URL and return the rendered HTML |
get_screenshot | Fetch a URL and return a screenshot |
get_file | Download a file (PDF, image, …) from a URL |
extract_page_data | Fetch a URL and extract specific data with CSS or XPath selectors |
fast_search | Fast web search returning clean organic results and top stories — the first choice for general searches |
get_google_search_results | Google SERP as JSON for specialised searches: news, maps, Lens, shopping, images, AI mode |
get_amazon_search_results | Amazon search results as JSON |
get_amazon_product_details | Amazon product details by ASIN |
get_amazon_pricing | Current Amazon price and seller offers by ASIN |
get_walmart_search_results | Walmart search results as JSON |
get_walmart_product_details | Walmart product details by ID |
get_youtube_search_results | YouTube search results |
get_youtube_video_metadata | Title, description, stats and more for a video |
get_youtube_video_subtitles | Subtitles / transcript for a video |
ask_chatgpt | Send a prompt to ChatGPT, optionally with web search |
ask_gemini | Send a prompt to Gemini, with citations when available |
get_scrapingbee_usage | Remaining credits and concurrency for your account |
Each call consumes API credits exactly as the equivalent ScrapingBee API request would (see pricing and the API documentation). The server handles one page or query per call; for hundreds of URLs, crawling a site, writing results to files or scheduling recurring jobs, use the ScrapingBee CLI.
Relevant keywords:
scrapingbee mcp
model context protocol server
mcp scraping
ai agent web scraping
mcp web scraping tool
What Is Model Context Protocol (MCP)?
Model Context Protocol (MCP) defines how AI systems interact with external tools in a structured way.
Instead of letting a language model guess how to scrape or browse the web, MCP allows it to:
- Discover available tools
- Call a tool using structured parameters
- Receive normalized JSON responses
- Inject results back into the reasoning loop
The ScrapingBee MCP server exposes web scraping capabilities as a formally registered tool that AI systems can use safely and predictably.
Why Use ScrapingBee with MCP?
AI models cannot reliably:
• Bypass anti-bot protections
• Manage proxy rotation
• Render JavaScript-heavy pages
• Handle CAPTCHA challenges
• Maintain scraping infrastructure
ScrapingBee handles all of that.
The MCP server acts as a bridge between your AI agent and ScrapingBee’s managed scraping infrastructure.
This enables true AI agent web scraping without fragile prompt-based hacks.
Architecture Overview
AI Agent
→ MCP Client
→ ScrapingBee MCP Server
→ ScrapingBee API
→ Target Website
→ Structured JSON Response
→ Injected Back Into Agent Context
The AI agent never scrapes directly.
It calls tools.
The MCP server executes them.
Installation
There is nothing to install or run: the server is operated by ScrapingBee at
https://mcp.scrapingbee.com/mcp. The only setup is your API key, which every client below
sends as a Authorization: Bearer header:
export SCRAPINGBEE_API_KEY=your_api_key
Connecting to the ScrapingBee MCP Server
You can connect in two ways:
- Via Claude Desktop (remote MCP)
- Via a custom Python MCP client
Option 1: Connect to Claude Desktop
Add the ScrapingBee MCP server to your claude_desktop_config.json file:
{
"mcpServers": {
"scrapingbee": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.scrapingbee.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer YOUR_API_KEY"
}
}
}
}
(The AUTH_HEADER variable works around mcp-remote's handling of spaces in arguments.)
This registers ScrapingBee as an MCP tool provider inside Claude Desktop.
After restarting Claude, the tools become available automatically.
Option 2: Custom Python MCP Client
For advanced AI workflows, you can build a minimal async MCP client using Python.
Below is a complete working example.
custom_mcp_client.py
import os
import re
import json
import asyncio
import httpx
import google.generativeai as genai
from typing import Dict, Any, List
MCP_SERVER_URL = "https://mcp.scrapingbee.com/mcp"
SCRAPINGBEE_API_KEY = os.environ.get("SCRAPINGBEE_API_KEY")
GEMINI_API_KEY = os.environ.get("GEMINI_API_KEY")
MCP Client Implementation
class MCPClient:
def __init__(self, base_url: str, api_key: str):
self.base_url = base_url
self.session_id = None
self.http_client = httpx.AsyncClient(timeout=300)
self.headers = {
"Authorization": f"Bearer {api_key}",
"Content-Type": "application/json",
"Accept": "application/json, text/event-stream",
"User-Agent": "Minimal-MCP-Client/1.0",
}
async def _send_request(self, payload: Dict[str, Any]):
headers = self.headers.copy()
if self.session_id:
headers["Mcp-Session-Id"] = self.session_id
response = await self.http_client.post(self.base_url, json=payload, headers=headers)
response.raise_for_status()
text = (await response.aread()).decode("utf-8")
if "data:" in text:
match = re.search(r"data:\s*({.*})", text, re.DOTALL)
if match:
return json.loads(match.group(1))
if response.status_code in [202, 204] or not text:
return {"status": "ok"}
return json.loads(text)
async def initialize(self):
init_payload = {
"jsonrpc": "2.0",
"id": "1",
"method": "initialize",
"params": {
"protocolVersion": "2024-11-05",
"capabilities": {},
"clientInfo": {"name": "MinimalClient"},
},
}
async with self.http_client.stream(
"POST", self.base_url, json=init_payload, headers=self.headers
) as response:
self.session_id = response.headers.get("Mcp-Session-Id")
notify_payload = {
"jsonrpc": "2.0",
"method": "notifications/initialized",
"params": {}
}
await self._send_request(notify_payload)
list_payload = {
"jsonrpc": "2.0",
"id": "2",
"method": "tools/list",
"params": {}
}
return await self._send_request(list_payload)
async def call_tool(self, tool_name: str, arguments: Dict[str, Any]):
payload = {
"jsonrpc": "2.0",
"id": "3",
"method": "tools/call",
"params": {
"name": tool_name,
"arguments": arguments
}
}
return await self._send_request(payload)
Converting MCP Tools for Gemini
def format_tools_for_gemini(tools: List[Dict[str, Any]]):
type_map = {
"string": genai.protos.Type.STRING,
"integer": genai.protos.Type.INTEGER,
"number": genai.protos.Type.NUMBER,
"boolean": genai.protos.Type.BOOLEAN,
}
gemini_tools = []
for tool in tools:
properties = {}
input_schema = tool.get("inputSchema", {})
if "properties" in input_schema:
for name, prop in input_schema["properties"].items():
properties[name] = genai.protos.Schema(
type=type_map.get(prop.get("type", "string")),
description=prop.get("description", "")
)
func = genai.protos.FunctionDeclaration(
name=tool["name"],
description=tool["description"],
parameters=genai.protos.Schema(
type=genai.protos.Type.OBJECT,
properties=properties,
required=input_schema.get("required", [])
),
)
gemini_tools.append(
genai.protos.Tool(function_declarations=[func])
)
return gemini_tools
Full AI → MCP → Tool Execution Flow
async def main():
mcp_client = MCPClient(MCP_SERVER_URL, SCRAPINGBEE_API_KEY)
tools_response = await mcp_client.initialize()
genai.configure(api_key=GEMINI_API_KEY)
gemini_tools = format_tools_for_gemini(tools_response["result"]["tools"])
model = genai.GenerativeModel(
model_name="gemini-2.5-pro",
tools=gemini_tools
)
user_prompt = input("Ask the AI to perform a task:\n> ")
response = model.generate_content(user_prompt)
function_call = response.candidates[0].content.parts[0].function_call
tool_name = function_call.name
tool_args = dict(function_call.args)
result = await mcp_client.call_tool(tool_name, tool_args)
print(json.dumps(result, indent=2))
What This Enables
With this architecture you can:
• Build AI agents that reason about available tools
• Allow LLMs to dynamically choose scraping actions
• Execute structured web data extraction
• Inject real-world data into model context
• Create scalable AI-native web scraping systems
Conclusion
The ScrapingBee MCP Server transforms web scraping into a structured, tool-driven data layer for AI systems.
Instead of brittle prompt scraping, you get:
• Model Context Protocol compliance
• JSON-RPC structured execution
• AI agent web scraping
• Scalable tool orchestration
This is AI-native web data access.
To start building AI-powered agents today, Get your free API key and connect to the ScrapingBee MCP server in minutes.
Comments
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.