DataForSEO MCP Setup: Complete Guide for 2026

DataForSEO is the data wholesaler behind a long list of SEO tools you already know. It ships its own server for the Model Context Protocol, now in a rebuilt v3 (the older v2 server is deprecated), which means you can point Claude, Cursor, or Claude Code straight at that data and ask SEO questions in plain language. It is genuinely powerful, the data is the real thing, and running the server itself costs nothing.

The catch is that a free server and a free tool are not the same thing. You bring your own DataForSEO account, fund it with a deposit, manage the credentials, and point your agent at a raw API. Done once, the setup is short. Done blind, it is a maze.

This guide walks the real setup, in order, for Claude Desktop, Cursor, and Claude Code. Then what to check when no tools show up, what the data actually costs, and an honest read on whether the raw MCP is the right call. If you would rather skip the wiring, ContextBolt SEO is the easier way in. Nothing to install beyond one URL, questions in plain language, every lookup saved to your SEO Dashboard, $35 a month after a 7-day free trial. The raw server below is the technical route, and a good one if you want the whole API on your own account. I run my own SEO inside an agent every day, so this is the workflow as it runs, not a feature list.

What is the DataForSEO MCP server?

The Model Context Protocol, or MCP, is an open standard from Anthropic that lets an AI agent call external tools and data through one common interface. If you are new to the idea, the what is MCP explainer covers the basics. The short version is that MCP is the plug, and a server is whatever you plug in.

The DataForSEO MCP server plugs the DataForSEO API into that interface. DataForSEO is a wholesale SEO data provider. It powers a large slice of the SEO products on the market behind the scenes, so the numbers it returns are the same class of data sitting inside dashboards you already trust. The open-source server lives on GitHub and gives your agent that data. The current v3 server is small by design. It has tools to browse the DataForSEO documentation and one tool that makes an authenticated API request, so the agent reads the docs and builds the call itself.

Once it is connected, you stop opening an SEO suite for quick questions. You ask the agent. Keyword volume, difficulty, live SERP results, domain traffic estimates, ranked keywords, competitor overlap, backlinks. The agent finds the right endpoint in the docs, makes the request, and the answer lands in your chat. If you want the full argument for why that beats another SEO suite, the SEO MCP server explainer makes the case.

What you need before you start

Three things, and the order matters.

• Node.js 22 or newer, for the local route: The local server runs through npx, which ships with Node. Check your version with node -v. If you are below 22, update first. The hosted URL does not need Node.
• A DataForSEO account: Sign up, then open the API dashboard and copy your API login and password. These are not your website login. They are a separate credential pair for API access.
• A funded balance: New accounts get a $1 trial credit, which is enough to test the connection. Real work needs a top-up, and the minimum deposit is $50. Nothing happens until the account has money, because every tool call spends it.

That third point trips people up. The server is free. The data is metered. You are paying DataForSEO directly, per request, with no middle layer smoothing it out.

How do you set up the DataForSEO MCP server?

There are two routes. The hosted server at https://mcp.dataforseo.com/v3/mcp signs you in with your DataForSEO account and needs nothing installed. The local server runs on your machine through npx and uses your API login and password. Pick the route and the client that match your tool.

Claude Code

This is the fastest. One command in your terminal registers the hosted server.

claude mcp add --transport http dataforseo \
  https://mcp.dataforseo.com/v3/mcp

Sign in with your DataForSEO account when Claude Code asks. To run the local server instead, pass your API credentials as environment variables.

claude mcp add dataforseo \
  --env DATAFORSEO_LOGIN=your-api-login \
  --env DATAFORSEO_PASSWORD=your-api-password \
  -- npx -y dataforseo-mcp-server@latest

The -y flag matters. Without it, npx stops to ask permission to install the package and hangs forever waiting for an answer you never see. Run claude mcp list afterward to confirm it registered.

Claude Desktop

Claude Desktop reads local servers from claude_desktop_config.json. Remote servers do not go in that file. To use the hosted server, open Customize, then Connectors, then the + button, then Add custom connector, and paste https://mcp.dataforseo.com/v3/mcp. On Team and Enterprise plans an Owner adds it under Organization settings, then Connectors. To run the local server instead, add this block to claude_desktop_config.json.

{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": ["-y", "dataforseo-mcp-server@latest"],
      "env": {
        "DATAFORSEO_LOGIN": "your-api-login",
        "DATAFORSEO_PASSWORD": "your-api-password"
      }
    }
  }
}

Everything hangs off the mcpServers key. Miss that key and the app ignores the whole file. After you save, fully quit and reopen the app. MCP servers only load at startup, and a window reload is not always enough.

Cursor

Cursor uses mcp.json, either globally at ~/.cursor/mcp.json or per project at .cursor/mcp.json. It accepts the hosted URL directly.

{
  "mcpServers": {
    "dataforseo": {
      "url": "https://mcp.dataforseo.com/v3/mcp"
    }
  }
}

The local block from the Claude Desktop section works in Cursor too. For a deeper walkthrough of the Cursor side specifically, the SEO inside Cursor guide covers it end to end.

That is the whole install. If your tools show up, you are done and can skip to the cost section. If they do not, the next part covers what to check.

Why are no tools showing up?

Older guides blame a variable called ENABLED_MODULES. That belonged to the deprecated v2 server, which had a tool for each family of endpoints. The current v3 server has no such variable, so if you copied it into a config, remove it.

For the local route, three things are worth checking in order.

• Node.js version: The current package needs Node.js 22 or newer. Run node -v and update if you are below that.
• Credentials: The local server needs DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD. DATAFORSEO_USERNAME is accepted as an alias for the login. These are your API credentials from the DataForSEO API access page, not your website login.
• Package version: Run the package as dataforseo-mcp-server@latest so you do not pick up an older cached copy, then fully quit and reopen the agent.

If you use the hosted URL, there are no credentials in the config. Your client signs you in with your DataForSEO account instead.

When it works, your agent sees four tools.

The API itself is still split into families such as SERP, Keywords Data, Labs, Backlinks and On-Page. The agent finds the right one through the documentation tools and then calls it with api_request. If you want to keep responses short, the server can trim them to a list of fields you choose in a config file.

What does the DataForSEO MCP actually cost?

This is where the “free” framing falls apart, so it is worth being precise.

The server costs nothing. The data is pure pay-as-you-go, billed by DataForSEO per request. Pricing starts at a fraction of a cent. A standard SERP query runs around $0.0006, with live real-time queries closer to $0.002, and the Labs endpoints priced per call in the same low range. There is no monthly subscription. You top the account up and draw it down.

The friction is not the per-request price, which is genuinely cheap. It is the shape. You fund a $50 minimum deposit up front, you watch a balance, and you manage credentials in every config file. For a developer who wants raw access to everything DataForSEO sells, that is a fair trade, and you get the whole catalog at wholesale prices. For someone who just wants to know if a keyword is winnable before they write the post, it is a lot of plumbing for one number. DataForSEO MCP pricing goes deeper on the pay-as-you-go model, including the two costs that never appear on the pricing page.

Is the raw DataForSEO MCP right for you?

Here is the take I will own the bias on, since we build a competing tool. The DataForSEO MCP is the right pick if you want the raw API on your own account, and most people who do their own SEO should not run it directly.

The reason is not the data. The data is excellent. It is that the raw server is built for developers, and it shows. You provision an account, fund a deposit, manage two credentials per machine, and then let your agent read the API docs and build raw requests that return raw API responses. None of that is hard. All of it is friction, and friction is the exact thing you connected an agent to remove. The whole point of asking your agent instead of opening a dashboard is to make a quick SEO question cost almost nothing. A server that takes an afternoon to wire up and a balance to babysit puts some of that cost back.

So the honest split looks like this.

If you are a developer who will use the breadth, run the raw server. If you want the answer without the setup project, ContextBolt SEO earns its keep. For the full field of options, the best SEO MCP servers roundup ranks all of them honestly, raw and hosted.

Where ContextBolt SEO fits

ContextBolt SEO is the wrapper we make, and it exists for the second column above. It is a hosted MCP server that sits on the same class of data and hands you one URL. You paste that URL into Claude Code, Claude Desktop, or Cursor, restart, and you have research tools in the chat for keyword research, keyword difficulty, SERP overviews, domain overviews, ranked keywords, and competitor keywords, plus backlinks, page and site audits, AI visibility, and a free read-only Search Console connection. No DataForSEO account, no $50 deposit, no credentials to copy into three config files. You start the trial, you get a URL, you work.

The raw server hands your agent the On-Page API and its wall of audit JSON. ContextBolt SEO turns that same class of data into a scored audit with a fix list worst first, and an agent with file access can work through the top items in the same chat and re-check.

Two things make the difference day to day. Every tool returns a digested answer with a verdict line, not a wall of JSON, so the chat stays readable while you work. And it remembers, so you can ask about the same keyword next month and get told what changed. The same lookups also land on your SEO Dashboard, which you can open and filter anytime, so the research is not stranded in one chat on one machine. That is the keyword research with Claude workflow with the setup tax removed.

The honest framing holds here too. This is Ahrefs-grade data, decision-useful and directionally accurate, not Ahrefs’ exact numbers. It costs $35 a month after a 7-day free trial, month to month, cancel any time, no long contract. For deciding what to build and what to write, it is more than enough, and it is a fraction of the entry price of the big suites.

The honest verdict

The DataForSEO MCP server is a real piece of work and the data behind it is the genuine article. If you are comfortable with a deposit, a balance, and a config file in every tool, it is serious SEO data at wholesale prices, and this guide is everything you need to run it.

But free-to-run is not free-to-use, and a developer tool is not a product. Most builders doing their own SEO want one thing from this setup. They want to ask a question and get a number, fast, without a context switch and without babysitting an account. If that is you, run the raw server only if you will use its breadth. Otherwise let ContextBolt SEO handle the plumbing. Paste one URL, ask in plain language, and the answer lands in the chat and on your SEO Dashboard. The first seven days are free, so you can spend your time on the writing instead of the wiring.