Skip to content
Oxylabs logo

How to connect the Oxylabs MCP server

To connect the official Oxylabs MCP server, add https://mcp.oxylabs.io/mcp to your MCP client as a Streamable HTTP server, then no sign-in is needed to connect. Oxylabs documents setup for Claude Code and Cursor.

Docs reviewed 5 Nov 2026Connection tested.

Try in the browser, no sign-in (via relay) → Oxylabs blocks requests from other websites, so the explorer uses API Tracker's relay. Anything you enter passes through it and is never stored or logged.

Endpoint https://mcp.oxylabs.io/mcp · Registry io.oxylabs/oxylabs-mcp 0.10.2

Add Oxylabs MCP to your client

.mcp.json
{
  "mcpServers": {
    "oxylabs": {
      "type": "http",
      "url": "https://mcp.oxylabs.io/mcp",
      "headers": {
        "Authorization": "Bearer ${OXYLABS_API_KEY}",
        "X-Oxylabs-AI-Studio-Api-Key": "${OXYLABS_X_OXYLABS_AI_STUDIO_API_KEY}"
      }
    }
  }
}
Set OXYLABS_API_KEYOXYLABS_X_OXYLABS_AI_STUDIO_API_KEY in your environment. Never paste keys into a shared file.

github.com/oxylabs

Connect Oxylabs MCP step by step

Before you start

  • At least one of: an Oxylabs Web Scraper API account (API token, or username and password, from the Oxylabs dashboard), or an Oxylabs AI Studio API key. Web Scraper API tools need the first; AI Studio tools need the second. github.com/oxylabs
  • A client that can send custom headers to a remote MCP server. OAuth is not supported, so clients that offer only OAuth sign-in can't pass the credentials. github.com/oxylabs
  • Oxylabs marks the repository behind this server as no longer supported. Its current MCP documentation describes a successor Web API server at a different endpoint. github.com/oxylabsdevelopers.oxylabs.io/ai-workflows

Authentication

Your client → Oxylabs MCP
No authentication. github.com/oxylabs
Oxylabs MCP → Oxylabs API
The server uses the API credential you supply. github.com/oxylabsThe server uses the API credential you supply. github.com/oxylabs

Steps

  1. Open the Oxylabs MCP server instructions

    github.com/oxylabs/oxylabs-mcp

  2. Add the Oxylabs MCP server to your client

    Add https://mcp.oxylabs.io/mcp as a remote MCP server that uses the HTTP transport, with the credential headers below. Oxylabs documents this for Claude Code and for Cursor or any client that supports remote servers with custom headers.

  3. For Web Scraper API tools: Authorization
  4. For AI Studio tools: X-Oxylabs-AI-Studio-Api-Key
  5. Choose how to send Web Scraper API credentials

    Oxylabs recommends sending your Web Scraper API token as a bearer token in the Authorization header. You can instead send your username and password with Basic authentication in the same header, or use the X-Oxylabs-Api-Token, X-Oxylabs-Username and X-Oxylabs-Password headers. If both a token and a username and password are sent, the token is used. Keep credentials in environment variables or a secret store.

  6. Consider Oxylabs' current Web API MCP server

    Oxylabs' current MCP documentation describes a hosted Web API server at https://mcp.oxylabs.io/web-api-mcp that authenticates with a Web API key in the Authorization header. It is a separate server from the one in this guide.

  7. List the server's tools

    Your client should list the server's tools. That confirms the connection, not every API permission.

What we observed

  • 5 Nov 2026: HTTP 200 without credentials: the server answered initialize with protocol version 2025-06-18 and server name oxylabs_mcp version 0.10.2. The publisher states that all tools are listed regardless of credentials and that calling a tool without the credentials it needs returns an error.
  • 5 Nov 2026: initialize and tools/list succeeded without credentials through the API Tracker relay (the endpoint refuses browser requests): 10 tools.

Oxylabs MCP questions

What is the Oxylabs MCP server URL?

The official Oxylabs MCP server is at https://mcp.oxylabs.io/mcp and uses the Streamable HTTP transport.

How do I authenticate with the Oxylabs MCP server?

No sign-in is needed to connect. Choose how to send Web Scraper API credentials: Oxylabs recommends sending your Web Scraper API token as a bearer token in the Authorization header. You can instead send your username and password with Basic authentication in the same header, or use the X-Oxylabs-Api-Token, X-Oxylabs-Username and X-Oxylabs-Password headers. If both a token and a username and password are sent, the token is used. Keep credentials in environment variables or a secret store.

Which AI clients can use the Oxylabs MCP server?

Oxylabs's documentation covers Claude Code and Cursor. Other clients that support remote Streamable HTTP MCP servers may also work.

What do I need before connecting Oxylabs MCP?

At least one of: an Oxylabs Web Scraper API account (API token, or username and password, from the Oxylabs dashboard), or an Oxylabs AI Studio API key. Web Scraper API tools need the first; AI Studio tools need the second. A client that can send custom headers to a remote MCP server. OAuth is not supported, so clients that offer only OAuth sign-in can't pass the credentials. Oxylabs marks the repository behind this server as no longer supported. Its current MCP documentation describes a successor Web API server at a different endpoint.

Has this Oxylabs MCP guide been tested?

Oxylabs's documentation was reviewed on 2026-11-05. The connection was tested.

Sources and review

Oxylabs's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.

Guide source and binding

MCP connection guide (draft 0.1) for io.oxylabs/oxylabs-mcp 0.10.2, bound to /remotes/0 of the Registry record by SHA-256 bd6abab297ed….

Guide JSON Source snapshot

Search API Tracker

Curated starting points