Decodo MCP Server

What Decodo MCP Server does

Decodo MCP Server gives MCP clients access to Decodo's web data services. Agents can retrieve pages as Markdown, capture webpage screenshots, enumerate site URLs, run asynchronous crawls, and search supported web destinations. The tool collection also includes purpose-built operations for Google, Amazon, Walmart, Target, TikTok, and YouTube.

The returned data is suited to both text-based and structured workflows. Markdown can be passed into an LLM or retrieval pipeline, screenshots provide visual page context, and target-specific tools return parsed results for searches, products, listings, posts, channels, and videos.

How it works

The server can be used through Decodo's hosted MCP endpoint at https://mcp.decodo.com/mcp, or run locally with the npm package or a build from the repository. Hosted connections send credentials in an Authorization header. Local connections provide the credential through the SCRAPER_API_TOKEN environment variable.

Web crawling is asynchronous. crawl_start returns a crawl identifier without waiting for completion; crawl_status reports discovered, completed, and failed pages; crawl_results reads completed pages in batches using a cursor; and crawl_cancel stops the crawl while keeping already collected pages available.

Tools are grouped into selectable toolsets. The documented groups include web, search, ecommerce, social_media, and ai. Hosted connections can select groups with the toolsets query parameter, while an unqualified connection registers all tools. The Claude connector exposes the web and search groups.

Setup and configuration

Create a Decodo account, obtain a Web Data API key from the dashboard, and use an MCP-compatible client. The local server requires Node.js 18 or newer. A hosted client configuration uses the following structure:

{
  "mcpServers": {
    "Decodo": {
      "url": "https://mcp.decodo.com/mcp",
      "headers": {
        "Authorization": "Bearer <api_key>"
      }
    }
  }
}

For a local npm configuration, run the package with npx and set SCRAPER_API_TOKEN:

{
  "mcpServers": {
    "Decodo": {
      "command": "npx",
      "args": ["-y", "@decodo/mcp-server"],
      "env": {
        "SCRAPER_API_TOKEN": "<api_key>"
      }
    }
  }
}

Older Decodo plans can use a basic authentication token in place of the API key. The same local environment variable accepts either credential type, while hosted connections use Bearer for an API key or Basic for the older token.

Tools and capabilities

• scrape_as_markdown fetches a URL and returns Markdown.
• screenshot captures a webpage as a PNG image.
• map lists URLs on a site without retrieving their content.
• crawl_start, crawl_status, crawl_results, and crawl_cancel manage multi-page crawls.
• search returns ranked web results.
• Google tools cover general search, ads, Lens, AI Mode, and Travel Hotels results.
• Amazon tools cover search, products, pricing, sellers, and bestsellers.
• Walmart and Target tools cover search and product pages.
• TikTok tools cover posts, Shop searches, Shop products, and Shop URLs.
• YouTube tools retrieve video metadata, channel videos, subtitles, and search results.

Limitations and notes

Several operations require an API key, including site mapping, crawling, and the general search tool. Access depends on the Decodo credential and service configuration. The hosted connection and local process use different credential locations, so switching between them requires changing the MCP configuration. Crawl results are returned incrementally rather than as one immediate response, and pagination uses a cursor.