Skip to main content
More information can be found in GitHub repository.
Connect LLMs and AI agents to live web data using MCP (Model Context Protocol). The Decodo MCP Server lets you scrape websites, search engines, eCommerce platforms, and social media directly from AI tools like Claude, Cursor, and Windsurf, all without the need to build scraping infrastructure from scratch.
  • Structured outputs in JSON, Markdown, and screenshots
  • Server-side JavaScript rendering and anti-bot handling
  • 125M+ IPs across 195+ locations

What is Decodo MCP server?

The Decodo MCP Server is a web scraping layer for AI agents. It connects MCP-compatible clients to Decodo’s Web Data API, enabling:
  • Web scraping for LLMs
  • Real-time data retrieval for RAG
  • AI agent browsing and research
  • Structured data extraction from dynamic websites
Instead of maintaining proxies, parsers, and retry logic, you get a single integration point for reliable web data access.

Why use MCP for web scraping?

Model Context Protocol (MCP) is the emerging standard for connecting AI agents to external tools and data sources. With MCP:
  • Agents can call tools dynamically
  • Integrations stay standardized
  • Workflows scale across environments
The Decodo MCP Server gives your agents reliable, production-ready web access through this standard.

Key features

Web scraping for AI agents, no infrastructure required. Scrape any website, including JavaScript-heavy pages, without handling proxy rotation, CAPTCHA solving, or anti-bot systems. Structured outputs for LLM workflows. Markdown (LLM-ready), JSON (for structured pipelines), and screenshots (for visual context), built for RAG pipelines, AI research agents, and automation flows. Built-in support for popular targets. Ready-made tools for Google (SERPs), Amazon, Walmart, and Target (eCommerce), TikTok and YouTube (social media), and Google AI Mode. Running the server yourself adds Bing, Google Ads, Google Lens, ChatGPT, and Perplexity (see Tools). Global proxy infrastructure. 115M+ residential IPs, 195+ geo-locations, and a 99.99% success rate on even the most protected targets. Modular MCP toolsets. Enable only what you need: web, search, ecommerce, social_media, ai for cleaner tool selection and better agent performance. Fast time to value. From API key to first scrape in minutes, no setup overhead.

Use cases

Use the Decodo MCP Server when you need web scraping for AI agents, structured data extraction at scale, reliable access to dynamic websites, real-time data for RAG, or an alternative to building scraping infrastructure from scratch. Common scenarios:
  • AI-powered web scraping – give LLMs the ability to collect fresh data instead of relying on static training data.
  • RAG with live data – pull real-time Google, Bing, and AI search results into retrieval pipelines.
  • eCommerce intelligence – track product prices, listings, and sellers across marketplaces without getting blocked.
  • Social media data collection – gather posts, channels, and engagement data from TikTok and YouTube.
  • Travel and price aggregation – build tools that collect live pricing and availability across websites.

Quick start

  1. Create a free account at dashboard.decodo.com – up to 10K free requests, no credit card required.
  2. Get an MCP client like Claude, Cursor, Windsurf, or any other MCP-compatible tool.
  3. Connect. If your client supports OAuth, add the server URL and sign in – no API key and nothing to install (see Sign in with OAuth). Otherwise, copy your Web Data API key from your Web Data API subscription on the dashboard and pass it as a header (see Authentication). Older plans have a basic authentication token, which also works.
  4. Configure the MCP server in your AI client (see configuration examples below).
You only need Node.js 22+ if you run the server locally with npx. The hosted server at https://mcp.decodo.com/mcp requires no installation.

Connecting to Decodo’s MCP server

Open your preferred MCP client and add the following configuration (see examples for Claude Code, Cursor, Windsurf below):

Authentication

The local server reads either credential from SCRAPER_API_TOKEN and works out which one it got.

Sign in with OAuth

The hosted server supports OAuth 2.1, so clients that implement it can connect without an API key. Add the server URL with no headers block at all:
Your client opens the Decodo dashboard, you approve the connection, and the client stores the token itself. There is no API key to copy and nothing to install.
OAuth support varies by client. If yours doesn’t offer a sign-in prompt, use the Authorization header shown above instead.

Claude Desktop

  1. Open Claude Desktop → Settings → Developer → Edit Config.
  2. Add to claude_desktop_config.json:
  1. Save and restart Claude Desktop.

Cursor

  1. Open Settings → MCP.
  2. Click Add a new global MCP server (opens mcp.json).
  3. Add the same configuration as above.
  4. Save — look for a green status indicator next to Decodo.

Windsurf

  1. Open Settings → Windsurf Settings.
  2. Scroll to Cascade → Add custom server + (opens mcp_config.json).
  3. Add the same configuration as above.
  4. Save and restart Windsurf.

Test your setup

Once connected, try this prompt in your client: ▎ “Scrape the titles of the top 5 articles from Hacker News” You should get a structured list back within seconds. If you see an auth error, double-check your API key on the dashboard.

Local development

Only needed if you want to change the server code.
PrerequisitesStep-by-step guide
  1. Clone the mcp-server repository:
  1. Run the following commands in the terminal:
  1. Take note of your build location:
Adding index.js to the end of this directory, your build file location should look something like this:
  1. Update your MCP client with the server information:

Toolsets

Tools are organized into toolsets. Which ones you get depends on how you connect.

Claude (official connector)

The Decodo connector in Claude’s connector directory is served from a dedicated endpoint, https://mcp.decodo.com/claude, and includes the Web Data API tools only. This set is fixed – the toolsets query parameter is ignored on this endpoint:

Any MCP client

You can selectively enable specific toolsets by passing a comma-separated list via the toolsets query parameter:
When no toolsets are specified, every toolset is enabled.
Nine tools are hidden on the hosted server by default and are available only when you run the server yourself: bing_search, google_ads, google_lens, chatgpt, perplexity, target_product, tiktok_shop_url, tiktok_post, and youtube_search.They are listed in the toolsets below because the toolsets describe the full server. In practice https://mcp.decodo.com/mcp exposes 24 of the 33 tools, so requesting ?toolsets=ai on the hosted server returns google_ai_mode only. If you run the server yourself, set HIDDEN_TOOLS= (empty) to enable all of them.

Tools

The server exposes the following tools. Tools marked Local only are hidden on the hosted server and work when you run the server yourself (see Toolsets).
Tools marked API key only reach the Web Data API, which basic authentication tokens cannot call. Using one returns: “This tool needs a Decodo API key; Basic authentication tokens cannot use the Web Data API.”

Parameters

The following parameters are inferred from user prompts:

Web Data API parameters

These apply to search, map, and the crawl_* tools.
limit defaults to 10, so an unqualified “crawl this site” returns 10 pages. Say how many you want – for example, “Crawl the first 200 pages of decodo.com/blog”.

Examples

Scraping geo-restricted content

Query your AI agent with the following prompt:
This prompt will say that peacock.com is geo-restricted. To bypass the geo-restriction:

Limiting number of response tokens

Long pages are truncated to tokenLimit characters (45000 by default) to avoid overflowing the context window. When content is cut, the result says so – “Truncated to N of M characters. Call again with a higher tokenLimit to get more.” – and when nothing was cut it confirms “Full website content retrieved.” You can raise the limit from your prompt:
If your agent has a big context window, tell it to return full content:

Support

Need help or just want to say hello? Our support is available 24/7.
You can also reach us anytime via email at support@decodo.com.

Feedback

Can’t find what you’re looking for? Request an article!
Have feedback? Share your thoughts on how we can improve.