workingproxysites.

Provider integration · Official publisher

ScrapingBee MCP

ScrapingBee MCP connects a remote client to search, page-reading and extraction tools. Start with the hosted endpoint and an Authorization header, then choose whether your task needs source discovery, readable text or selected fields. The setup below keeps the API key out of the endpoint URL.

Server publisher: ScrapingBee. Guide maintained by Working Proxy Sites.

Documentation reviewed · Next review

What you can use it for

  • Find source URLs with the web search tool.
  • Read a page in Markdown or text.
  • Extract selected fields from a page.

Documented capabilities: Web search · Scraping & extraction.

Account & usage

Account required
Yes
Required product
ScrapingBee API account.
Billing basis
Calls consume API credits according to the chosen features and proxy options; account plan limits apply. Provider pricing.

When to choose ScrapingBee MCP

A useful fit when

  • Research that starts with a search query and continues to source pages.
  • Extracting selected page fields through a hosted API.

Check another approach when

  • Proxy purchases or account provisioning: the selected tools do not establish those operations.
Sources: ScrapingBee published tool catalog, ScrapingBee hosted MCP documentation

Connect to ScrapingBee MCP

Choose a connection profile below and replace credential placeholders in your own MCP client. The transport describes the MCP connection.

Hosted MCP

Streamable HTTP · hosted

Endpoint
https://mcp.scrapingbee.com/mcp
Authentication
Authorization: Bearer followed by a ScrapingBee API key.

Before you connect

  • ScrapingBee account and API key.
  • A remote MCP client accepting custom headers.

Cursor mcp.json (JSON) Sources: ScrapingBee hosted MCP documentation, Cursor MCP configuration reference

Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Configuration guide.

{
  "mcpServers": {
    "scrapingbee": {
      "url": "https://mcp.scrapingbee.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Example workflow: find a source, read it, then extract fields

A suggested sequence using the documented tools. Check the connected server's tool schema before making a call.

  1. Discover candidate pages

    Ask for a small set of relevant source URLs and choose which ones to inspect. A search result is a lead, not a substitute for the page itself.

    Tools: fast_search

    Sources: ScrapingBee published tool catalog
  2. Read the chosen source

    Retrieve readable page content before asking the model to summarize it. Keep the source URL with your notes.

    Tools: get_page_text

    Sources: ScrapingBee published tool catalog
  3. Extract the fields you need

    For a repeatable output, name the required fields and use the documented extraction options. Check the returned values against the source.

    Tools: extract_page_data

    Sources: ScrapingBee published tool catalog

Selected tools & example tasks

Troubleshoot the connection

A request uses more credits than expected

Review rendering and proxy options before increasing the request volume. Feature choices can change consumption; a single tool call is not a fixed universal credit amount.

Sources: ScrapingBee pricing

Limits & undocumented behavior

  • The hosted endpoint needs a Bearer API key header. The older api_key URL parameter is deprecated.
  • Requests can consume different numbers of credits when rendering or proxy options change.
  • The reviewed tool documentation does not establish proxy purchasing or proxy account management.

ScrapingBee MCP: questions & answers

Which ScrapingBee tool should I use first?

Use fast_search when you need URLs, get_page_text when the URL is known, and extract_page_data when you need selected fields.

Sources: ScrapingBee published tool catalog
Can I use the older api_key URL parameter?

The provider labels that query parameter deprecated. Use the documented Bearer header setup in a client that supports it.

Sources: ScrapingBee hosted MCP documentation
Does installing MCP make ScrapingBee usage free?

No. The MCP interface uses your ScrapingBee API account. Product limits and feature-dependent credit usage still apply.

Sources: ScrapingBee pricing

Sources & review history

This listing is documentation-confirmed. We reviewed the primary sources below; this is not a successful live connection test.

Record updated . Review due .

  1. ScrapingBee hosted MCP documentationChecked · Official endpoint, Streamable HTTP, Bearer authentication and deprecated query-key setup
  2. ScrapingBee published tool catalogChecked · Current selected search, page and extraction tool names
  3. ScrapingBee pricingChecked · API credits and feature-dependent consumption
  4. Cursor MCP configuration referenceChecked · Client JSON format and remote header support

Spotted a change? Share the source and the affected setup step in Site Feedback.

Alternatives to ScrapingBee MCP

These integrations share documented capabilities with ScrapingBee MCP. Compare their setup and product requirements for your task.

Apify MCP

Find Apify Actors, inspect their inputs and pricing, run a selected Actor, and retrieve its dataset through the official MCP server.

Shared capabilities
Web search · Scraping & extraction
Connection choices
Streamable HTTP · Local stdio
Product to check
Apify Actors and platform usage
Compare setup & authentication →

Bright Data MCP

Search the public web, retrieve page content and use optional browser tools through Bright Data’s hosted or local MCP integration.

Shared capabilities
Web search · Scraping & extraction
Connection choices
Streamable HTTP · Local stdio
Product to check
Bright Data Web Unlocker API; additional products may be used by optional tools.
Compare setup & authentication →

Decodo MCP

Retrieve pages, search results and supported structured targets through Decodo’s Web Scraping API.

Shared capabilities
Web search · Scraping & extraction
Connection choices
Streamable HTTP
Product to check
Decodo Web Scraping API.
Compare setup & authentication →

Evomi MCP

Inspect Evomi proxy products, targeting and usage, rotate sessions, and run scraping jobs through a local Python MCP server.

Shared capabilities
Web search · Scraping & extraction
Connection choices
Local stdio
Product to check
Evomi Public API access plus the proxy or Scraper API product used by the tool.
Compare setup & authentication →