Web Scraper MCP Server

Decodo MCP Server

This repository provides a Model Context Protocol (MCP) server that connects LLMs and applications to Decodo's platform. The server facilitates integration between MCP-compatible clients and Decodo's services, streamlining access to our tools and capabilities.

Features

• Easy web data access. Simplified retrieval of information from websites and online sources.
• Geographic flexibility. Access content regardless of regional restrictions.
• Enhanced privacy. Browse and collect data while maintaining anonymity.
• Reliable scraping. Advanced techniques to avoid detection and blocks.
• Simple integration. Seamless setup with popular MCP clients like Claude Desktop, Cursor, and Windsurf.

Authenticating

1. Go to decodo.com and start a Web Scraping API plan (free plan available).

2. Once your plan has started, obtain a Web Scraping API basic authentication token from the dashboard.

Connecting to Decodo's MCP server (Claude Code, Cursor)

1. Open your preferred MCP client and add the following configuration:

{
  "Decodo": {
    "url": "https://mcp.decodo.com/mcp",
    "headers": {
      "Authorization": "Basic <basic_auth_token>"
    }
  }
}

Claude Desktop

{
  "mcpServers": {
    "Decodo MCP Server": {
      "command": "npx",
      "args": ["@decodo/mcp"],
      "env": {
        "SCRAPER_API_TOKEN": "<web_scraping_api_base64_token>",
        "TOOLSETS": "web,ai"
      }
    }
  }
}

Running the MCP server locally

Prerequisites

• Node.js 18.0+
• An MCP client - popular choices are Claude Desktop and Cursor

Step-by-step guide

1. Clone this repository:

git clone https://github.com/Decodo/decodo-mcp-server

1. Run the following commands in the terminal:

cd decodo-mcp-server
npm install
npm run build

1. Take note of your build location:

cd build/
pwd

Adding index.js to the end of this directory, your build file location should look something like this:

/Users/your.user/projects/decodo-mcp/build/index.js

1. Update your MCP client with the server information:

{
  "mcpServers": {
    "decodo-mcp": {
      "command": "node",
      "args": ["/Users/your.user/projects/decodo-mcp/build/index.js"],
      "env": {
        "SCRAPER_API_TOKEN": "<web_scraping_api_base64_token>"
      }
    }
  }
}

Toolsets

Tools are organized into toolsets. You can selectively enable specific toolsets by passing a comma-separated list via the toolsets query parameter:

    "Decodo MCP Server": {
      "url": "https://mcp.decodo.com/mcp?toolsets=web,ai",
      "headers": {
        "Authorization": "Basic <your_auth_token>"
      }
    }

When no toolsets are specified, all tools are registered.

Tools

The server exposes the following tools:

Parameters

The following parameters are inferred from user prompts:

Examples

Scraping geo-restricted content

Query your AI agent with the following prompt:

Scrape peacock.com from a German IP address and tell me the pricing.

This prompt will say that peacock.com is geo-restricted. To bypass the geo-restriction:

Scrape peacock.com from a US IP address and tell me the pricing.

Limiting number of response tokens

If your agent has a small context window, the content returned from scraping will be automatically truncated, in order to avoid context-overflow. You can increase the number of tokens returned within your prompt:

Scrape hacker news, return 50k tokens.

If your agent has a big context window, tell it to return full content:

Scrape hacker news, return full content.

Related repositories

Web Scraping API

Google Maps scraper

Amazon scraper

License

All code is released under the MIT License.