workingproxysites.

Provider integration · Official publisher

Oxylabs MCP

Oxylabs MCP documents tools for Web Scraper API and AI Studio. Those product families use different credentials. Oxylabs' product MCP documentation now features a separate server, oxylabs/web-api-mcp, for its Web API and does not list this one; this page records documented setup without claiming a successful live connection.

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

Documentation reviewed · Next review

What you can use it for

  • Retrieve a web page with the Web Scraper API.
  • Collect parsed search results.
  • Use AI Studio browser tasks with an AI Studio key.

Documented capabilities: Web search · Scraping & extraction · Browser automation.

Account & usage

Account required
Yes
Required product
Oxylabs Web Scraper API for the included setup; AI Studio requires its own key.
Billing basis
Web Scraper API plans bill by successful results, with target and rendering affecting consumption. AI Studio has separate product usage terms. Provider pricing.
Server software license
MIT

When to choose Oxylabs MCP

A useful fit when

  • Existing Oxylabs customers matching a documented tool to a product they can access.
  • Search and page extraction using Web Scraper API credentials.

Check another approach when

  • Oxylabs Web API users: Oxylabs' MCP documentation points them to the separate oxylabs/web-api-mcp server.
  • Assuming a listed AI Studio tool works with only Web Scraper API credentials.
Sources: Oxylabs official MCP repository, Oxylabs MCP documentation

Connect to Oxylabs MCP

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

Hosted MCP — Web Scraper API credentials

Streamable HTTP · hosted

Endpoint
https://mcp.oxylabs.io/mcp
Authentication
Web Scraper API token in Authorization: Bearer (recommended) or X-Oxylabs-Api-Token. Alternatively, username and password via Authorization: Basic or the X-Oxylabs-Username/X-Oxylabs-Password headers.

Before you connect

  • Oxylabs Web Scraper API token (or username and password).
  • A remote MCP client accepting custom headers.

Cursor mcp.json (JSON) Sources: Oxylabs official MCP repository, Cursor MCP configuration reference

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

{
  "mcpServers": {
    "oxylabs": {
      "url": "https://mcp.oxylabs.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Match the task to the product before calling a tool

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

  1. Discover relevant sources

    Use google_search_scraper for a bounded search. Pick source URLs that answer the research question rather than treating a result listing as the full source.

    Tools: google_search_scraper

    Sources: Oxylabs official MCP repository
  2. Retrieve and inspect page content

    Use universal_scraper for selected URLs and the required output format. Review whether rendering is needed, because target and rendering choices can affect Web Scraper API consumption.

    Tools: universal_scraper

    Sources: Oxylabs official MCP repository, Oxylabs billing explanation
  3. Use AI Studio only for a matching task

    If the task needs the documented browser agent, supply the separate AI Studio credential before calling ai_browser_agent. Keep the requested interaction bounded and inspect its result.

    Tools: ai_browser_agent

    Sources: Oxylabs official MCP repository

Selected tools & example tasks

Troubleshoot the connection

A listed tool reports missing credentials.

Match the tool to its product family. Hosted HTTP can advertise tools before the required product credentials are supplied.

Sources: Oxylabs official MCP repository

Scraping works but the browser agent fails authorization.

Check X-Oxylabs-AI-Studio-Api-Key. A Web Scraper username and password do not provide AI Studio authentication.

Sources: Oxylabs official MCP repository

Limits & undocumented behavior

  • The official repository is no longer archived (commits on 2026-10-15 added API-token auth). Oxylabs' current MCP documentation does not list this server; it points Web API users to a separate server, oxylabs/web-api-mcp. WPS has not run an authenticated connection test against the hosted endpoint.
  • This setup enables Web Scraper API requests. AI Studio tools require an additional X-Oxylabs-AI-Studio-Api-Key header.
  • Hosted tools may be listed without their required credentials; those calls fail until the correct product credentials are supplied.
  • The reviewed tool documentation does not establish proxy purchasing or proxy account management.

Oxylabs MCP: questions & answers

Why does the local tool list differ from the hosted list?

All tools are always listed, both locally and hosted; calling a tool without its product credentials returns an error explaining what to configure.

Sources: Oxylabs official MCP repository
Is this the server Oxylabs documents for its Web API?

No. Oxylabs' product MCP documentation points Web API users to the separate oxylabs/web-api-mcp server and does not list this one. This repository is active again, but WPS has not tested a live authenticated connection.

Sources: Oxylabs official MCP repository, Oxylabs MCP documentation
Which credentials do Oxylabs MCP tools need?

Web Scraper API uses an API token or its username and password; AI Studio uses its own API key. Configure the credential family for the tools you intend to call.

Sources: Oxylabs official MCP repository

Sources & review history

This listing is documentation-confirmed. We reviewed the primary sources below; this does not establish successful tool execution.

Record updated . Review due .

  1. Oxylabs official MCP repositoryChecked · Publisher, hosted headers and token authentication, product-specific tools and MIT license
  2. Oxylabs billing explanationChecked · Web Scraper API result-based billing
  3. Cursor MCP configuration referenceChecked · Client JSON format and remote header support
  4. Oxylabs MCP documentationChecked · Current product MCP documentation lists oxylabs-web-api-mcp for Web API, not this server

Spotted a change? Send the source and the affected setup step to our contact address.

Alternatives to Oxylabs MCP

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

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 · Browser automation
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 →

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 · Browser automation
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 →

Firecrawl MCP

Choose keyless, OAuth or API-key access to Firecrawl search and extraction tools. Check which operations need an account before connecting your client.

Shared capabilities
Web search · Scraping & extraction · Browser automation
Connection choices
Streamable HTTP
Product to check
Keyless hosted Search, Scrape and Parse; a Firecrawl account/team for authenticated tools.
Compare setup & authentication →

Novada MCP

Search, extract pages, use browser tools and configure proxy connections through Novada’s hosted endpoint or local npm package.

Shared capabilities
Web search · Scraping & extraction · Browser automation
Connection choices
Streamable HTTP · Local stdio
Product to check
Novada account with access to the scraping, browser or proxy product selected by the tool.
Compare setup & authentication →