MCP Ecommerce

Installation guide

How to install DataForSEO MCP Server

In Claude, ChatGPT, Gemini, Microsoft Copilot, Perplexity, Cursor and Claude Code, with what to check before you start and the first prompts to run.

DataForSEO offers two routes. The local route runs `npx dataforseo-mcp-server` on your machine with your API login and password set as environment variables. The hosted route uses the streamable HTTP endpoint `https://mcp.dataforseo.com/mcp` with no local setup. The documentation says the hosted endpoint is for supported clients other than Claude, and that most modern clients (except Claude Desktop) expect the HTTP protocol.

Whoever owns the DataForSEO account should do this, using the API login and password, which are not the dashboard login. Every call spends DataForSEO balance, so start with small, read-only lookups and check the balance afterwards. The vendor has separate guides for Claude Desktop, Claude Code, Gemini CLI, ChatGPT, Docker, Cursor and n8n, plus an OAuth guide for the remote server. Use those for exact client-specific values.

DataForSEO MCP Server setup guide: DataForSEO's MCP documentation page on dataforseo.com, shown in a browser frame (seo MCP server for e-commerce)
DataForSEO MCP Server setup guide preview: DataForSEO’s documentation on dataforseo.com, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

  • A DataForSEO account with API credentials (API login and API password, not your dashboard login).
  • Funded DataForSEO balance, since every call is billed against it.
  • The latest Node.js, if you use the local npx route (old versions cause a "Fetch not defined" error).
  • An MCP-compatible client such as Claude Code, Cursor, Gemini CLI or ChatGPT.
  • For ChatGPT with the remote server: your your_api_login:your_api_password encoded in Base64 for an authorization header.
How it runs
Remote or local
Access
Read-only
Server address
https://mcp.dataforseo.com/mcp

DataForSEO MCP Server in Claude

  1. The documentation says the HTTP protocol and the remote endpoint are not for Claude Desktop. Use the default stdio mode locally instead.
  2. Open the vendor's Claude (Desktop) quick setup guide from the DataForSEO help center and take the exact config from it.
  3. In Claude Desktop, open the MCP configuration (Settings > Developer, or the connectors area) and add a local server entry that runs npx dataforseo-mcp-server.
  4. Set DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD to your API login and password in the entry's environment.
  5. Restart Claude Desktop and confirm the DataForSEO tools are listed.
claude_desktop_config.json
{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": [
        "dataforseo-mcp-server"
      ],
      "env": {
        "DATAFORSEO_USERNAME": "your_username",
        "DATAFORSEO_PASSWORD": "your_password"
      }
    }
  }
}

DataForSEO MCP Server in ChatGPT

  1. The documentation says ChatGPT with the remote server needs an authorization header. Follow the vendor's ChatGPT guide for exact steps.
  2. Base64-encode your_api_login:your_api_password and build the header as Basic <encoded value>.
  3. In ChatGPT, enable Developer mode and add a custom MCP connector (the docs do not cover the menu path).
  4. Enter the URL https://mcp.dataforseo.com/mcp and supply the authorization header.
  5. Save, enable the connector in a chat, and run a small read-only test.
Connector URL
https://mcp.dataforseo.com/mcp

DataForSEO MCP Server in Gemini

  1. Open the vendor's Connect Gemini CLI to DataForSEO MCP Server guide and take the exact settings from it.
  2. For the local route, add an entry under mcpServers in the Gemini CLI settings file that runs npx dataforseo-mcp-server.
  3. Provide DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD in the entry's env.
  4. Start Gemini CLI and check that the DataForSEO tools are listed.
  5. Run one small keyword lookup to confirm.
Gemini CLI settings (mcpServers)
{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": [
        "dataforseo-mcp-server"
      ],
      "env": {
        "DATAFORSEO_USERNAME": "your_username",
        "DATAFORSEO_PASSWORD": "your_password"
      }
    }
  }
}

DataForSEO MCP Server in Microsoft Copilot

  1. The documentation does not cover Microsoft Copilot Studio or GitHub Copilot, so use each product's standard way of adding an MCP server.
  2. For GitHub Copilot in VS Code, add a server to .vscode/mcp.json under servers, using the command npx with the argument dataforseo-mcp-server.
  3. Set DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD in the entry's env, ideally via VS Code input variables rather than plain text.
  4. For Copilot Studio, add an MCP tool by URL using https://mcp.dataforseo.com/mcp, and check the vendor's OAuth guide for the auth method.
  5. Start the server and run a small read-only test.
.vscode/mcp.json
{
  "servers": {
    "dataforseo": {
      "command": "npx",
      "args": [
        "dataforseo-mcp-server"
      ],
      "env": {
        "DATAFORSEO_USERNAME": "your_username",
        "DATAFORSEO_PASSWORD": "your_password"
      }
    }
  }
}

DataForSEO MCP Server in Perplexity

  1. The documentation does not mention Perplexity, so use the app's standard way of adding a custom MCP connector.
  2. Open the connectors area in the Perplexity desktop app and choose to add a custom or remote connector.
  3. Enter the URL https://mcp.dataforseo.com/mcp.
  4. Supply your API login and password as the app requests. The exact auth format is not in the docs, so check the vendor's OAuth guide.
  5. Run a small read-only test and check your DataForSEO balance.
Connector URL
https://mcp.dataforseo.com/mcp

DataForSEO MCP Server in Cursor

  1. Open the vendor's Cursor quick setup guide and take the exact config from it.
  2. Open Cursor's MCP settings and add a new server, or edit the MCP JSON file.
  3. Use the command npx with the argument dataforseo-mcp-server for the local route.
  4. Set DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD in env.
  5. Save, confirm the server shows as enabled with its tools listed, then run a small test.
Cursor MCP JSON
{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": [
        "dataforseo-mcp-server"
      ],
      "env": {
        "DATAFORSEO_USERNAME": "your_username",
        "DATAFORSEO_PASSWORD": "your_password"
      }
    }
  }
}

DataForSEO MCP Server in Claude Code

  1. Open the vendor's Claude Code quick setup guide to confirm the exact command.
  2. Make sure the latest Node.js is installed.
  3. Run claude mcp add with the local command npx dataforseo-mcp-server, passing your credentials as environment variables.
  4. Note that the documentation says the remote endpoint is not for Claude, so prefer the local route.
  5. Run claude mcp list to confirm the server is registered, then try a small keyword lookup.
Terminal
claude mcp add dataforseo -e DATAFORSEO_USERNAME=your_username -e DATAFORSEO_PASSWORD=your_password -- npx dataforseo-mcp-server

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

  • Look up search volume for one keyword in one location. Do not run more than one request.
  • List the DataForSEO tools you can access and say which ones are read-only.
  • Show the top 10 Google organic results for one keyword, and tell me roughly what the request cost.

Troubleshooting

+Why do I get "you are not authorized" errors?

This is the most common issue. Check that you used your API login and password, not your dashboard login. Credential format also varies by client. Some take separate fields, while ChatGPT with the remote server needs a Base64 `Basic` authorization header. Follow the vendor guide for your client.

+Why do I see a "Fetch not defined" error?

The documentation attributes this to an old Node.js version. Install the latest Node.js, restart your terminal or client so it picks up the new version, and run `npx dataforseo-mcp-server` again. Confirm the client launches the same Node installation you updated.

+Why does the server not work in Claude Desktop over HTTP or the hosted URL?

The documentation says the HTTP protocol and the hosted endpoint are for clients other than Claude, and that most modern clients except Claude Desktop expect HTTP. In Claude Desktop use the default stdio mode through `npx dataforseo-mcp-server`, and follow the vendor's Claude guide.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.