Thordata MCP Server

Connect Thordata SERP to MCP-compatible AI agents and clients for real-time search, usage history, and statistics.

The Thordata SERP MCP Server exposes Thordata search capabilities through the Model Context Protocol (MCP), making it easy to integrate live search tools into agents, workflows, and MCP clients. In addition to real-time SERP requests, it also provides access to search history, usage statistics, and engine schema resources for richer integrations.

Official MCP Registry

This server is published in the official MCP Registry as io.github.Thordata/thordata-mcp.

View the official Registry entry

The Registry entry points to the hosted Thordata MCP endpoint and provides standardized connection metadata for compatible clients.

Quick start

Most users connect to the hosted Thordata MCP endpoint — no installation, no local build. You only need a Thordata SERP API key.

1. Get your API key

Sign up at Thordata and get your SERP API key from the dashboard.

2. Connect your MCP client

Point your MCP client at the hosted endpoint and put your API key in the URL path. Your key is used per request; Thordata never stores a shared credential on your behalf.

The default connection URL is:

https://mcp.thordata.com/YOUR_API_KEY/mcp

Replace YOUR_API_KEY with your Thordata SERP API key and use this MCP client configuration:

{
  "mcpServers": {
    "thordata": {
      "url": "https://mcp.thordata.com/YOUR_API_KEY/mcp"
    }
  }
}

If your client supports custom headers, you can instead use the Bearer configuration:

{
  "mcpServers": {
    "thordata": {
      "url": "https://mcp.thordata.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Dataset tools

Dataset tools use the same unified API key as SERP tools. The path token, Authorization: Bearer, and X-API-Key all carry the same key, so no separate dataset credential is required:

{
  "mcpServers": {
    "thordata": {
      "url": "https://mcp.thordata.com/YOUR_API_KEY/mcp"
    }
  }
}

If your client can set headers, either form works:

{
  "mcpServers": {
    "thordata": {
      "url": "https://mcp.thordata.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

X-API-Key is still supported and overrides the path token for dataset tools when both are present. If no API key is supplied, the dataset tools return dataset_credential_required.

fetch_dataset is page-based: each call returns at most 10 records and charges the wallet once for that page. The first call creates an order_id; keep calling with order_id, cursor, and page_no until next_cursor is empty. All pages share one order in the wallet and backend.

Use list_datasets to see the dataset packages currently available to your account. get_dataset_info returns the price and limits for one dataset_key. Neither call charges the wallet.

Web Scraper tools

Web Scraper uses the same Dataset/Web Scraper API key. The MCP server supports exactly these seven products:

Read thordata://web-scrapers or call list_web_scrapers to obtain the current public field schema.

... View full README on GitHub