ScrapingBee
com.scrapingbeev2.2.0Updated Oct 8, 2026
Scrape any web page, search Google/Amazon/Walmart/YouTube and extract data via the ScrapingBee API.
Overview
AI-generated overview
Lets an assistant scrape web pages and run searches on Google, Amazon, Walmart and YouTube through the ScrapingBee API.
- What it does
- This remote MCP server connects an assistant to the ScrapingBee API so it can fetch and extract data from arbitrary web pages. It also supports running searches on Google, Amazon, Walmart and YouTube and returning the results. The manifest lists no individual tools, so the exact tool set is not documented here.
- When to use it
- Worth adding when an assistant needs live web content or search results from those engines and you already use ScrapingBee, or want its proxy and rendering handling instead of fetching pages directly.
- Requirements
- A remote streamable HTTP endpoint at mcp.scrapingbee.com; nothing runs locally. It requires an Authorization header carrying a ScrapingBee API key as a bearer token, obtained from the ScrapingBee account page. Network access to the endpoint is needed.
Before you install
The Authorization header carries a ScrapingBee API key, so treat it as a secret and avoid exposing it in logs or shared configs. ScrapingBee is a paid service, so requests may consume account credits or incur charges. Scraped pages and search queries are sent to a third party, and scraping may be subject to site terms of service.
Installation
In SourceWeft
- Open ScrapingBee in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://mcp.scrapingbee.com/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v2.2.0LatestOct 8, 2026

