workingproxysites.

Provider integration · Official publisher

ScrapeOps MCP

ScrapeOps MCP is suited to a small pipeline: find useful links on a page, inspect a candidate, then request structured data. Its three tools expose the Proxy API through the assistant while leaving the choice of target pages and extraction schema visible.

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

Documentation reviewed · Next review

What you can use it for

  • Discover links from a starting page.
  • Extract product or job data into JSON.
  • Inspect content with optional rendering and screenshots.

Documented capabilities: Scraping & extraction.

Account & usage

Account required
Yes
Required product
ScrapeOps Proxy API Aggregator
Billing basis
The MCP server uses the Proxy API product, whose plans meter API credits for successful requests and impose concurrency limits. This differs from the separate Residential and Mobile Proxy Aggregator billing by bandwidth. Provider pricing.
Server software license
MIT

When to choose ScrapeOps MCP

A useful fit when

  • Product or job extraction that needs structured output.
  • Starting from a category page and selecting its relevant links.

Check another approach when

  • Looking for a Google Maps search tool based on the maps_web name.
  • Assuming MCP usage follows the separate bandwidth-priced proxy product.
Sources: ScrapeOps official MCP release notes, ScrapeOps product pricing

Connect to ScrapeOps MCP

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

ScrapeOps local MCP

Local stdio · local

Package / runtime
@scrapeops/mcp
Authentication
ScrapeOps API key in the SCRAPEOPS_API_KEY environment variable.

Before you connect

  • Node.js 22 or later with npx.
  • A ScrapeOps API key and available Proxy API credits.

Local stdio mcp.json — replace the credential placeholders Sources: ScrapeOps MCP reference, ScrapeOps official MCP release notes, Official ScrapeOps MCP repository

{
  "mcpServers": {
    "scrapeops-stdio": {
      "command": "npx",
      "args": [
        "-y",
        "@scrapeops/mcp"
      ],
      "env": {
        "SCRAPEOPS_API_KEY": "YOUR_SCRAPEOPS_API_KEY"
      }
    }
  }
}

Discover links and extract a sample

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

  1. Choose candidate pages

    Collect links from a starting page, then select a small set relevant to the requested record type.

    Tools: return_links

    Sources: ScrapeOps official MCP release notes
  2. Inspect one candidate

    Retrieve a sample page. Add rendering or a screenshot if necessary to understand what content is available.

    Tools: maps_web

    Sources: ScrapeOps official MCP release notes, ScrapeOps Proxy API quick start
  3. Request structured output

    Use domain parsing or an LLM schema for the selected page. Check required fields in the first result before scaling to more candidates.

    Tools: extract_data

    Sources: ScrapeOps MCP reference

Selected tools & example tasks

Troubleshoot the connection

The package will not launch.

Check that the client can find npx and is using Node.js 22 or later. Set SCRAPEOPS_API_KEY in the server environment.

Sources: ScrapeOps MCP reference

Requests appear to time out while usage increases.

Check the client timeout. The underlying Proxy API can retry for up to two minutes; a client may stop waiting before a successful request completes.

Sources: ScrapeOps Proxy API quick start

Limits & undocumented behavior

  • The documented package requires Node.js 22 or later.
  • Proxy options apply to scraping requests; these tools do not establish a proxy-account management interface.
  • Documentation-confirmed; no live authenticated extraction was performed.

ScrapeOps MCP: questions & answers

Is maps_web a Google Maps search tool?

The documented tool retrieves a supplied URL. Its name does not establish a dedicated Maps search endpoint.

Sources: ScrapeOps MCP reference
Should I choose extract_data or maps_web?

Choose extract_data for structured records. Use maps_web to inspect the page or its rendered appearance before deciding what to extract.

Sources: ScrapeOps official MCP release notes
Which ScrapeOps pricing model applies here?

This MCP server exposes the Proxy API, priced with successful-request credits. The separate Residential and Mobile product uses bandwidth billing.

Sources: ScrapeOps product 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. ScrapeOps MCP referenceChecked · Package configuration, runtime requirement and tool parameters.
  2. ScrapeOps official MCP release notesChecked · Published tools, extraction capabilities and local deployment.
  3. ScrapeOps Proxy API quick startChecked · Request options, timeouts and account usage visibility.
  4. ScrapeOps product pricingChecked · Successful-request credit plans versus bandwidth plans.
  5. Official ScrapeOps MCP repositoryChecked · Official implementation, stdio startup, tool behavior and MIT license.

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

Alternatives to ScrapeOps MCP

These integrations share documented capabilities with ScrapeOps 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
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
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 →

Crawlbase MCP

Retrieve HTML or Markdown, capture rendered pages, and revisit stored crawl results through Crawlbase tools.

Shared capabilities
Scraping & extraction
Connection choices
Local stdio
Product to check
Crawlbase Crawling API and Cloud Storage
Compare setup & authentication →

Decodo MCP

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

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