Oxylabs MCP Server

Created By
oxylabsa year ago
Official Oxylabs MCP integration
Overview

What is Oxylabs MCP?

Oxylabs MCP is a Model Context Protocol server that allows AI assistants to access web data through advanced web scraping technology.

How to use Oxylabs MCP?

To use Oxylabs MCP, set up the server with your Oxylabs account credentials and make requests to scrape web pages or extract data using the provided API parameters.

Key features of Oxylabs MCP?

  • Scrape content from any website, including JavaScript-heavy pages.
  • Automatically clean and convert HTML to Markdown for better readability.
  • Bypass anti-scraping measures and geo-restrictions with rotating IPs.
  • Flexible setup with cross-platform support for macOS, Windows, and Linux.
  • Built-in error handling and request management.

Use cases of Oxylabs MCP?

  1. Extracting product data from e-commerce sites.
  2. Scraping search results from Google or other search engines.
  3. Collecting data from news websites or blogs for analysis.

FAQ from Oxylabs MCP?

  • Can I scrape any website using Oxylabs MCP?

Yes, you can scrape any website, including those with complex structures and anti-scraping measures.

  • Is there a free trial available?

Yes, Oxylabs offers a one-week free trial for new users.

  • What programming languages are supported?

The server is primarily built with Python and can be used with Node.js for CLI commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
oxylabs
Star
33
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago