Oxylabs MCP Server – Web Data for AI Agents
Oxylabs MCP Server connects MCP-compatible clients to Oxylabs web data collection services. It lets AI agents scrape URLs, retrieve search and ecommerce data, use AI-powered extraction workflows, and work with public web data through configured Oxylabs credentials.
Overview
Oxylabs MCP Server is the official Oxylabs Model Context Protocol integration for connecting AI agents to Oxylabs web data tools. It is designed for workflows where an agent needs current public web information rather than relying only on static model knowledge. Depending on the credentials provided, the server exposes tools for Oxylabs Web Scraper API, Oxylabs AI Studio, or both.
What the MCP server enables
With Web Scraper API credentials, the server can expose tools for general URL scraping, Google Search scraping, Amazon search result scraping, and Amazon product page extraction. With an Oxylabs AI Studio API key, it can expose AI-powered tools for scraping a URL into JSON or Markdown, crawling a site based on a prompt, controlling a browser agent, and searching the web for URLs and contents.
The available tools are credential-dependent. If only Web Scraper API username and password are configured, only the Web Scraper API tools are available. If only an AI Studio API key is configured, only AI Studio tools are available. Providing both credential sets enables all documented tools.
When to use it
Use this MCP server when an AI assistant needs public web data for research, competitive monitoring, search-result retrieval, ecommerce page analysis, RAG input collection, or prompt-driven extraction from websites. It is especially useful when the target pages require JavaScript rendering, structured extraction, or Oxylabs infrastructure rather than a simple HTTP fetch.
Connection and authentication
The documented local setup uses stdio with uvx oxylabs-mcp. Authentication is configured through environment variables: OXYLABS_USERNAME and OXYLABS_PASSWORD for Web Scraper API, and OXYLABS_AI_STUDIO_API_KEY for AI Studio. LOG_LEVEL may be set to control returned logs.
The official repository also documents a hosted Smithery URL configuration, including OAuth2 flow or query-parameter credential configuration. This file includes the local stdio option because it keeps credentials in the client environment and avoids placing secrets in a URL.
Key considerations
Do not leave placeholder credentials in the client configuration. The Oxylabs server uses the presence of credential variables to decide which tool groups to expose, so invalid placeholder values can expose tools that will not work. Use credentials with the least privilege suitable for the task, keep them out of source control, and ensure scraping activities comply with applicable laws, target-site restrictions, and Oxylabs product terms.
Supported Transports
stdio
Command: uvx
Args:
oxylabs-mcp
Frequently Asked Questions
- When should an AI agent use Oxylabs MCP Server?
- Use it when an agent needs live public web data, such as scraping a URL, collecting Google Search results, extracting Amazon product data, crawling a site from a prompt, or building AI-ready web context for research and RAG workflows.
- What tools can Oxylabs expose through MCP?
- The official server documents Web Scraper API tools including universal_scraper, google_search_scraper, amazon_search_scraper, and amazon_product_scraper, plus AI Studio tools including ai_scraper, ai_crawler, ai_browser_agent, and ai_search.
- Why do the available tools depend on credentials?
- Oxylabs MCP Server automatically exposes tool groups based on configured credentials. Web Scraper API username and password expose Web Scraper API tools, an AI Studio API key exposes AI Studio tools, and providing both exposes all documented tool groups.
- How is authentication configured for Oxylabs MCP Server?
- For local stdio usage, configure `OXYLABS_USERNAME` and `OXYLABS_PASSWORD` for Web Scraper API access and/or `OXYLABS_AI_STUDIO_API_KEY` for AI Studio access. Store the real values securely in the MCP client environment, not in this YAML file.
- Which transport should be used for Oxylabs MCP Server?
- Use the local stdio transport with `uvx oxylabs-mcp` when you want credentials kept in local environment variables. The official repository also documents a Smithery-hosted URL option, but this YAML keeps the direct local server setup.