Oxylabs Mcp

io.oxylabsPublished by oxylabs.ioOfficial publisherv0.10.2Updated Oct 29, 2026

Fetch and process content from specified URLs & sources using the Oxylabs Web Scraper API.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping Browser Automation

Server details

Identifier: io.oxylabs/oxylabs-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to oxylabs.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.oxylabs%2Foxylabs-mcp.svg)](https://sourceweft.com/mcp/io.oxylabs%2Foxylabs-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Oxylabs MCP lets an assistant scrape, crawl, search and browse the web through Oxylabs APIs, returning clean structured or Markdown data.

What you can do: Search the web and scrape any URL, with optional JavaScript rendering and Markdown, HTML, JSON, CSV or TOON output
Crawl a site from a starting URL and map its URLs, filtered by keywords or a prompt
Drive a real browser to navigate, click links, fill forms and scroll, then return the result
Scrape Google Search and Amazon search or product pages with parsing, pagination, locale and geolocation options
Generate an OpenAPI-format JSON schema for structured extraction
When to use it: Useful when an assistant needs live web data that plain fetching cannot reach: JavaScript-heavy pages, CAPTCHA or geo-restricted sites, search results, or multi-page crawls and structured extraction from Google or Amazon.
Requirements: Either the hosted endpoint at mcp.oxylabs.io with credentials in headers, or the oxylabs-mcp PyPI package run locally with uv/uvx. Needs an Oxylabs Web Scraper API token or username and password, and/or an Oxylabs AI Studio API key, passed as OXYLABS_API_TOKEN, OXYLABS_USERNAME and OXYLABS_PASSWORD, OXYLABS_AI_STUDIO_API_KEY, or the Authorization and X-Oxylabs-AI-Studio-Api-Key headers. Paid accounts; free trials and credits are mentioned.

Before you install

Requires paid Oxylabs credentials: an API token or username and password, plus an AI Studio API key; only set variables you actually have, since placeholders break calls. Scraped URLs, queries and prompts are sent to Oxylabs' servers and its proxy network. The README states the repository is no longer supported and points to newer MCP repositories. Clients that only support OAuth cannot pass the required headers.

Installation

In SourceWeft

Open Oxylabs Mcp 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.oxylabs%2Foxylabs-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "oxylabs": {
      "type": "http",
      "url": "https://mcp.oxylabs.io/mcp"
    }
  }
}

README

[Oxylabs + MCP]

Oxylabs MCP Server

The missing link between AI models and the real‑world web: one API that delivers clean, structured data from any site.

[pypi package] [Image] [Licence] [Verified on MseeP] [Coverage badge]

[Oxylabs Server MCP server]

Disclaimer

This repository is no longer supported and being worked on. Kindly check our latest MCP repositories: Web API MCP Agent Browser MCP

📖 Overview

The Oxylabs MCP server provides a bridge between AI models and the web. It enables them to scrape any URL, render JavaScript-heavy pages, extract and format content for AI use, manage CAPTCHA, and access geo-restricted web data from 195+ countries.

It is built on the Model Context Protocol (MCP), the open standard for connecting AI assistants to external tools and data.

mcp-name: io.oxylabs/oxylabs-mcp

🛠️ MCP Tools

Oxylabs MCP provides two sets of tools that can be used together or independently:

Oxylabs Web Scraper API tools

universal_scraper: scrapes any URL, with optional JavaScript rendering, geo-targeting, and Markdown/HTML/links output;
google_search_scraper: extracts results from Google Search, with optional parsing into structured JSON;
amazon_search_scraper: scrapes Amazon search result pages, with optional parsing into structured JSON;
amazon_product_scraper: extracts data from individual Amazon product pages.

Oxylabs AI Studio tools

ai_scraper: scrapes content from any URL with AI-powered extraction, in JSON, CSV, Markdown, or TOON format;
ai_crawler: crawls a website from a starting URL based on a prompt and collects data across multiple pages;
ai_browser_agent: controls a real browser based on a prompt — navigates, clicks, fills forms — and returns the result;
ai_search: searches the web and optionally returns Markdown content of each result;
ai_map: maps a website's URLs, filtered by keywords or a prompt;
generate_schema: generates an OpenAPI-format JSON schema for structured extraction with the AI tools above.

✅ Prerequisites

Before you begin, make sure you have at least one of the following:

Oxylabs Web Scraper API account: obtain an API token (or your username and password) from the Oxylabs dashboard (1-week free trial available);
Oxylabs AI Studio API key: obtain your API key from Oxylabs AI Studio (1000 credits free).

To run the server locally (Option 2 below) you will also need the uv package manager:

📦 Configuration

There are two ways to use the server: connect to the hosted instance (no installation) or run it locally with credentials in environment variables.

Option 1: Hosted server (no installation)

Oxylabs runs a hosted MCP server at:

Credentials are passed with request headers:

Credential	Header
Web Scraper API token (recommended)	`Authorization: Bearer <token>`
Web Scraper API token (alternative)	`X-Oxylabs-Api-Token`
Web Scraper API username and password	`Authorization: Basic <base64(username:password)>`
Web Scraper API username and password (alt.)	`X-Oxylabs-Username` and `X-Oxylabs-Password`
AI Studio	`X-Oxylabs-AI-Studio-Api-Key`

If both an API token and a username and password are passed, the token is used.

Setup with Claude Code:

bash

claude mcp add --transport http oxylabs https://mcp.oxylabs.io/mcp \  --header "Authorization: Bearer YOUR_API_TOKEN" \  --header "X-Oxylabs-AI-Studio-Api-Key: YOUR_API_KEY"

claude mcp add --transport http oxylabs https://mcp.oxylabs.io/mcp \  --header "Authorization: Bearer YOUR_API_TOKEN" \  --header "X-Oxylabs-AI-Studio-Api-Key: YOUR_API_KEY"

Setup with Cursor or any client that supports remote MCP servers with custom headers:

json

{  "mcpServers": {    "oxylabs": {      "url": "https://mcp.oxylabs.io/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_TOKEN",        "X-Oxylabs-AI-Studio-Api-Key": "YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "oxylabs": {      "url": "https://mcp.oxylabs.io/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_TOKEN",        "X-Oxylabs-AI-Studio-Api-Key": "YOUR_API_KEY"      }    }  }}

The server is also listed on Smithery.

Note: clients that only support OAuth for remote servers (for example, adding a custom connector in the claude.ai web UI) cannot pass headers yet — OAuth sign-in is on our roadmap. Use the local setup below with those clients in the meantime.

Option 2: Run locally

Environment variables

Oxylabs MCP server supports the following environment variables:

Name	Description	Default
`OXYLABS_API_TOKEN`	Your Oxylabs Web Scraper API token
`OXYLABS_USERNAME`	Your Oxylabs Web Scraper API username
`OXYLABS_PASSWORD`	Your Oxylabs Web Scraper API password
`OXYLABS_AI_STUDIO_API_KEY`	Your Oxylabs AI Studio API key
`LOG_LEVEL`	Log level for the logs returned to the client	`INFO`

For the Web Scraper API tools, set either OXYLABS_API_TOKEN or both OXYLABS_USERNAME and OXYLABS_PASSWORD. If both are set, the token is used. For the AI Studio tools, set OXYLABS_AI_STUDIO_API_KEY.

All tools are always listed; calling a tool without the credentials it needs returns an error message explaining what to configure.

❗ Important: only set the environment variables you have real credentials for. Placeholder values make tool calls fail.

Configure with uvx

Installs the package from PyPI and runs it automatically:

json

{  "mcpServers": {    "oxylabs": {      "command": "uvx",      "args": ["oxylabs-mcp"],      "env": {        "OXYLABS_API_TOKEN": "YOUR_API_TOKEN",        "OXYLABS_AI_STUDIO_API_KEY": "YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "oxylabs": {      "command": "uvx",      "args": ["oxylabs-mcp"],      "env": {        "OXYLABS_API_TOKEN": "YOUR_API_TOKEN",        "OXYLABS_AI_STUDIO_API_KEY": "YOUR_API_KEY"      }    }  }}

Configure with a local checkout

Useful for development — runs the server from a local clone of this repository:

json

{  "mcpServers": {    "oxylabs": {      "command": "uv",      "args": [        "--directory",        "/<absolute-path-to-folder>/oxylabs-mcp",        "run",        "oxylabs-mcp"      ],      "env": {        "OXYLABS_API_TOKEN": "YOUR_API_TOKEN",        "OXYLABS_AI_STUDIO_API_KEY": "YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "oxylabs": {      "command": "uv",      "args": [        "--directory",        "/<absolute-path-to-folder>/oxylabs-mcp",        "run",        "oxylabs-mcp"      ],      "env": {        "OXYLABS_API_TOKEN": "YOUR_API_TOKEN",        "OXYLABS_AI_STUDIO_API_KEY": "YOUR_API_KEY"      }    }  }}

Running as a remote HTTP server (self-hosting)

The server also supports the MCP streamable-HTTP transport. Start it with:

With the HTTP transport, credentials are passed per request instead of environment variables:

Credential	How to pass it
Web Scraper API token (recommended)	`Authorization: Bearer <token>`
Web Scraper API token (alternative)	`X-Oxylabs-Api-Token` header
Web Scraper API username and password	`Authorization: Basic <base64(username:password)>` (HTTP Basic auth)
Web Scraper API username and password (alt.)	`X-Oxylabs-Username` and `X-Oxylabs-Password` headers
AI Studio	`X-Oxylabs-AI-Studio-Api-Key` header

Example client configuration:

json

{  "mcpServers": {    "oxylabs": {      "url": "https://your-host:8000/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_TOKEN",        "X-Oxylabs-AI-Studio-Api-Key": "YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "oxylabs": {      "url": "https://your-host:8000/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_TOKEN",        "X-Oxylabs-AI-Studio-Api-Key": "YOUR_API_KEY"      }    }  }}

All tools are always listed regardless of provided credentials; calling a tool without the credentials it needs returns an error message explaining exactly what to configure.

Setup with Claude Desktop

Navigate to Claude → Settings → Developer → Edit Config and add one of the configurations above to the claude_desktop_config.json file.

Setup with Cursor AI

Navigate to Cursor → Settings → Cursor Settings → MCP. Click Add new global MCP server and add one of the configurations above.

📝 Logging

The server provides additional information about the tool calls in notification/message events:

json

{  "method": "notifications/message",  "params": {    "level": "info",    "data": "Create job with params: {\"url\": \"https://ip.oxylabs.io\"}"  }}

{  "method": "notifications/message",  "params": {    "level": "info",    "data": "Create job with params: {\"url\": \"https://ip.oxylabs.io\"}"  }}

json

{  "method": "notifications/message",  "params": {    "level": "info",    "data": "Job info: job_id=7333113830223918081 job_status=done"  }}

{  "method": "notifications/message",  "params": {    "level": "info",    "data": "Job info: job_id=7333113830223918081 job_status=done"  }}

json

{  "method": "notifications/message",  "params": {    "level": "error",    "data": "Error: request to Oxylabs API failed"  }}

{  "method": "notifications/message",  "params": {    "level": "error",    "data": "Error: request to Oxylabs API failed"  }}

✨ Key Features

Scrape content from any site

Extract data from any URL, including complex single-page applications
Fully render dynamic websites using headless browser support
Choose full JavaScript rendering, HTML-only, or none
Emulate Mobile and Desktop viewports for realistic rendering

Automatically get AI-ready data

Automatically clean and convert HTML to Markdown for improved readability
Use automated parsers for popular targets like Google, Amazon, and more

Manage CAPTCHA & geo-restrictions

Navigate sophisticated automated request management systems with high success rate
Reliably scrape even the most complex websites
Get automatically rotating IPs from a proxy pool covering 195+ countries

Flexible setup & cross-platform support

Set rendering and parsing options if needed
Feed data directly into AI models or analytics tools
Works on macOS, Windows, and Linux

Built-in error handling and request management

Comprehensive error handling and reporting
Smart rate limiting and request management

Why Oxylabs MCP? 🕸️ ➜ 📦 ➜ 🤖

Imagine telling your LLM "Summarise the latest Hacker News discussion about GPT‑5" – and it simply answers. The Oxylabs MCP server makes that happen by doing the boring parts for you:

What Oxylabs MCP does	Why it matters to you
Manages automated request walls with the Oxylabs global proxy network	Enables website access and anonymity
Renders JavaScript in headless Chrome	Single‑page apps, sorted
Cleans HTML → Markdown	Drop straight into vector DBs or prompts
Optional structured parsers (Google, Amazon, etc.)	One‑line access to popular targets

🛡️ License

Distributed under the MIT License – see LICENSE for details.

About Oxylabs

Established in 2015, Oxylabs is a market-leading web intelligence collection platform, driven by the highest business, ethics, and compliance standards, enabling companies worldwide to unlock data-driven insights.

[image]

_{Made with ☕ by Oxylabs. Feel free to give us a ⭐ and a follow if our MCP saved you a weekend.}

Solutions made based on this MCP:

Michelin Detour

Source: README.md at commit bbdf3e3

Tools

ai_crawler

Tool useful for crawling a website from starting url and returning data in a specified format. Schema is required only if output_format is json, csv or toon. 'render_javascript' is used to render javascript heavy websites. 'return_sources_limit' is used to limit the number of sources to return, for example if you expect results from single source, you can set it to 1.

Parametersurlrequiredschemauser_promptrequiredgeo_locationoutput_formatrender_javascriptreturn_sources_limit

ai_scraper

Scrape the contents of the web page and return the data in the specified format. Schema is required only if output_format is json or csv. 'render_javascript' is used to render javascript heavy websites.

Parametersurlrequiredschemageo_locationoutput_formatrender_javascript

ai_browser_agent

Run the browser agent and return the data in the specified format. This tool is useful if you need navigate around the website and do some actions. It allows navigating to any url, clicking on links, filling forms, scrolling, etc. Finally it returns the data in the specified format. Schema is required only if output_format is json, csv or toon. 'task_prompt' describes what browser agent should achieve

Parametersurlrequiredschematask_promptrequiredgeo_locationoutput_format

ai_search

Search the web based on a provided query. 'return_content' is used to return markdown content for each search result. If 'return_content' is set to True, you don't need to use ai_scraper to get the content of the search results urls, because it is already included in the search results. if 'return_content' is set to True, prefer lower 'limit' to reduce payload size.

Parameterslimitqueryrequiredgeo_locationreturn_contentrender_javascript

generate_schema

Generate a json schema in openapi format.

Parametersapp_namerequireduser_promptrequired

ai_map

Tool useful for mapping website's URLs.

Parametersurlrequiredlimituser_promptgeo_locationmax_crawl_depthsearch_keywordsallow_subdomainsrender_javascriptallow_external_domains

universal_scraper

Get a content of any webpage. Supports browser rendering, parsing of certain webpages and different output formats.

Parametersurlrequiredrendergeo_locationoutput_formatuser_agent_type

google_search_scraper

Scrape Google Search results. Supports content parsing, different user agent types, pagination, domain, geolocation, locale parameters and different output formats.

Parameterslimitpagesparsequeryrequireddomainlocalerenderad_modestart_pagegeo_locationoutput_formatuser_agent_type

amazon_search_scraper

Scrape Amazon search results. Supports content parsing, different user agent types, pagination, domain, geolocation, locale parameters and different output formats. Supports Amazon specific parameters such as category id, merchant id, currency.

Parameterspagesparsequeryrequireddomainlocalerendercurrencystart_pagecategory_idmerchant_idgeo_locationoutput_format+1 more

amazon_product_scraper

Scrape Amazon products. Supports content parsing, different user agent types, domain, geolocation, locale parameters and different output formats. Supports Amazon specific parameters such as currency and getting more accurate pricing data with auto select variant.

Parametersparsequeryrequireddomainlocalerendercurrencygeo_locationoutput_formatuser_agent_typeautoselect_variant

Version history

v0.10.2LatestOct 29, 2026
v0.9.1Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Oxylabs integrations

Oxylabs

Published by GitHub account pipeworx-io

Pipeworx gateway endpoint for the Oxylabs Web Scraper API, letting an assistant scrape pages, run Google searches and pull Amazon product data.

Streamable HTTPWeb executable

Web Search & Scraping47 toolsNov 4, 2026