DataForSEO MCP review: version 3 cut the server from 89 tools to 4

By Jan Suski. I go deep on every review, checking every number against its source and digging up details other coverage misses, a habit from six years of SEO and link building for tech companies. Bylines at Surfer, Brand24, and Senuto. How the scoring works.

Published 23 September 2026Prefer this source on Google

SEO

Test the server on a trial balance

Try DataForSEO

$1 in free credit lands on signup, and a $50 minimum top-up covers 25,000 live SERP pages at list price.

Visit DataForSEO →

May earn a commission if you sign up through this link, at no extra cost to you. Full affiliate disclosure.

DataForSEO MCP is the Model Context Protocol server DataForSEO publishes for its own APIs. It lets an AI assistant pull live SERP results, keyword volumes, backlinks and on-page audits from a plain-language prompt, without anyone writing code, and it has been public since 22 May 2025. The code sits in the open-source mcp-server-typescript repository under an Apache-2.0 licence, with 242 stars and 118 forks on 23 September 2026.

The server changed shape in August 2026. Version 2 exposed one MCP tool per endpoint, 89 of them, and a July measurement put that tool list at 42,288 tokens. Version 3 replaced all of it with four tools that read the API documentation first and then make one generic request.

This review of the DataForSEO MCP server covers v3: setup across MCP clients, what it costs per request, how far the help center lags the code, and how it stacks up against the Semrush, Ahrefs and Bright Data servers. The DataForSEO API review covers the data underneath in more depth, and this page covers the step after it, making the API work inside an AI client.

↑ FACT SHEETWhat the DataForSEO MCP server does after the v3 redesign

The v2 DataForSEO MCP implementation drew four GitHub issues over context size, numbered 10, 14, 27 and 57. On 21 July 2026 varun29ankuS, who builds an open-source MCP checker, filed a measurement on GitHub:

Your server exposes 89 tools totalling 42,288 tokens (gpt-4o tokenizer, exact count). That entire surface is sent to the model on every turn, before the user types anything

GitHub issue #57, varun29ankuS, 21 July 2026

His cohort of 29 public MCP servers had a median tool list of 1,679 tokens, which put DataForSEO at roughly 25 times the median. He corrected one point in the same thread: "Claude Code and Codex now defer MCP tool schemas by default." The 42,288 figure is the worst case, paid in full by clients that don't defer.

DataForSEO's answer arrived on 18 August 2026. A maintainer wrote that "starting with DataForSEO MCP Server v3.0, we've released a substantially rethought version," and the v3 README lists four MCP tools:

• docs_index returns the API documentation index, filterable by section and cached for 24 hours.
• docs_list_sections returns the section names.
• docs_search fetches one documentation page, with optional code examples.
• api_request makes the authenticated call to any DataForSEO endpoint.

The new implementation changes how an agent works. The model now spends one or two docs lookups before making each request. In exchange, an agent connected to eight other servers carries four DataForSEO tools, down from 89.

Responses got smaller too. By default api_request calls the AI-optimized .ai version of each endpoint, which strips empty fields, rounds floats to three decimals and sets depth and limit to 10. The .ai format costs nothing extra, and setting noAiMode to true switches back to the standard paths. Both formats come out of the same implementation, so a team can copy a prompt between them unchanged.

Oversized responses drew the oldest open issue on the repository. It was filed 27 August 2025 by 62316e and still describes the problem:

First of all: nice tool. The problem is that JSON returned from those tools are way too big. I'm always getting "Your input exceeds the context window of this model. Please adjust your input and try again." I'm using gpt-5-mini (Input: 272,000 Output: 128,000).

GitHub issue #27, 62316e, 27 August 2025

↑ FACT SHEETQuick start: connecting MCP clients over streamable HTTP or stdio

The remote DataForSEO MCP server is the fastest route. Copy https://mcp.dataforseo.com/v3/mcp into a client that speaks streamable HTTP and sign in, since OAuth 2.0 authentication is the default on HTTP. Clients discover the authorization server through protected-resource metadata and send a Bearer token from then on.

Running the MCP server locally takes Node.js, a DataForSEO account and your API login. Create the account first, then copy the credentials from the API Access tab. The JSON block below is an example config for Claude Desktop or Cursor, with the command, args and env keys most clients expect:

{
  "mcpServers": {
    "dataforseo": {
      "command": "npx",
      "args": ["dataforseo-mcp-server@latest"],
      "env": {
        "DATAFORSEO_LOGIN": "your_api_login",
        "DATAFORSEO_PASSWORD": "your_api_password"
      }
    }
  }
}

Setup is easy for anyone who has edited a JSON config before, and Gemini CLI or Claude Code users can copy the same block into their own config files. The local build runs over stdio by default, which suits local development. Adding --mode http starts a streamable HTTP server on port 3000, or whatever the PORT variable says. On HTTP the server checks for credentials in a fixed order: a Basic authorization header, then a Bearer token, then the environment variables.

Keep an eye on the version string. SushiBob reported error 40501 on a language_code parameter in May 2026, and a maintainer traced it to npx serving an old cached build. The fix was forcing a fresh copy with the -y flag on npx dataforseo-mcp-server@latest, and his reply was short:

Thank you that worked :) Appreciate the fast response! Bob

GitHub issue #45, SushiBob, 19 May 2026

Client integration has broken before. In August 2025, jlightfoot found Gemini CLI skipping 25 tools with the message "because it has missing types in its parameter schema," after a filter schema change in commit 0a3954c. That issue is closed, and v3's four-tool surface leaves fewer schemas to break.

Other build targets ship in the repository: a Dockerfile, a Cloudflare Worker build, and a CLI mode that runs docs and request commands without an MCP client at all. The CLI mode is a recent addition, handy for a quick and dirty check of credentials before any client is configured, and the same npx dataforseo-mcp-server command drives both stdio and CLI use.

Help center docs lag the v3 server

The devil's in the details on setup, because DataForSEO's own pages disagree. The MCP product page and the v3 README give https://mcp.dataforseo.com/v3/mcp as the server URL. Two help center guides give different paths:

• The Claude Code guide, updated 15 May 2026, adds the server with claude mcp add --header "Authorization: Basic <basic_auth_token>" --transport http dfs-mcp https://mcp.dataforseo.com/http.
• The ChatGPT guide, updated 5 May 2026, points to https://mcp.dataforseo.com/mcp with a Base64 Basic header entered under Custom headers. The guide says to copy that header from the API Access tab, where a Send by Email button mails the credentials already encoded.

The Node.js requirement drifts the same way. The MCP page and the Claude Code guide say 18 or higher. The v3 README says 20. The npm manifest for version 3.1.1 declares node >=22, and that's the floor npm enforces on install.

A user troubleshooting a failed connection has three URLs to choose from, and each wrong pick sends setup back to square one. The Claude Code guide tells Windows users that editing .claude.json directly is "the most reliable approach."

↑ FACT SHEETPricing, the $50 minimum and payment methods

The DataForSEO MCP server costs nothing to run. DataForSEO's SEO MCP page states the connection is free and open source, with data billed pay-as-you-go against a prepaid balance. A new account gets a $1 trial credit, and the pricing page sets the minimum payment at $50. Credits never expire.

Per-request rates from the SERP API pricing page and the MCP page:

• Standard queue SERP: $0.0006 per page of 10 results, $600 per million.
• Priority queue SERP: $0.0012 per page.
• Live SERP: $0.002 per page, the mode an agent waiting on an answer uses.
• 100 related keywords: about $0.024 in API usage.
• Backlink summary: $0.024 plus $0.000036 per row.

Price it against your own workload

Run the numbers on DataForSEO

Standard SERP pages cost $0.0006 each and live pages $0.002, billed against a prepaid balance that never expires.

View DataForSEO pricing →

May earn a commission if you sign up through this link, at no extra cost to you. Full affiliate disclosure.

At those rates $50 covers 25,000 live SERP pages. A solo SEO sending 400 live SERP calls a week spends $3.20 a month, a drop in the bucket next to the $129 Ahrefs Lite plan.

Hacker News users have said the same about the API for years. In a 2022 comment, vgeek called it "going to be the cheapest/easiest route" for keyword volume, adding "it is basically like $0.10 (don't quote me, but around there) to fetch monthly search volume for <700 terms per batch." In 2021 he compared it directly with the subscription model:

This is probably the most economical option. Semrush and Ahrefs have APIs that may be of interest, but they have a monthly subscription vs just purchasing credits.

Hacker News comment, vgeek, 29 November 2021

Payment methods listed on the pricing page are Visa, Mastercard, PayPal. The $50 floor is the catch for a first test. Before v3, carlenns hit a context error on the first prompt and weighed the price of finding out:

I even just disabled all of the Backlinks tools yet I still get this issue. Any suggestions ? Does a subscription tier enable the mcp server to work ? I have not tried that yet as I am in Canada and $28 US is a lot to test if something works.

GitHub issue #14, carlenns, 6 July 2025

The full rate card, queue by queue, sits in the DataForSEO pricing report.

Which DataForSEO API modules and SEO data the MCP tools reach

api_request reaches every module on the MCP page's list, so the module choice happens in the prompt. That makes the DataForSEO MCP server a single integration point for all DataForSEO APIs and services. The four that carry most SEO data work:

• SERP API: live and queued results for Google, Bing and other engines.
• DataForSEO Labs: keyword research, with search-intent labels for up to 1,000 keywords per request and historical keyword data back to August 2021, per the Labs keyword research page.
• Backlinks API: backlinks, referring domains and anchors.
• On-Page API: crawl-based audits, including Lighthouse runs.

Keywords Data, AI Optimization, Business Data and Domain Analytics round out the set, and the Content Analysis API sits behind the same api_request tool. SEO professionals tracking brand mentions and sentiment for a client reach it with the same prompt pattern as a SERP pull, since content analysis runs through that API. Labs caps usage at 2,000 API calls per minute across its endpoints.

Field filtering is the tool for anyone who needs to zero in on a few columns. A JSON config passed with --configuration, or through FIELD_CONFIG_PATH or FIELD_CONFIG_JSON, trims each endpoint's response by path. Webmasterei asked for exactly that in June 2025:

Hi, I love your tool but with claude desktop I often run into a "too many charakters in message" situations. Mainly it is about search volume history I absolutely dont' need in my keyword research context.

GitHub issue #10, Webmasterei, 17 June 2025

Is DataForSEO legit?

Yes. DataForSEO has run since 2011 as in-house tooling and as a public data company since 2016. Its about page lists over 3,500 customers, a 99.95% uptime guarantee, and ISO certification from 2021, which it bills as a first for a martech data provider. Nick Chernets is the CEO, and the site footer reads "Built with love in Ukraine."

Developers mostly cite the price. In a Hacker News comment from September 2024, umussetu described asking an AI coding tool "to integrate with https://dataforseo.com/ api which is 10x cheaper than the ahrefs or semrush apis (it's real data)."

↑ FACT SHEETDataForSEO MCP vs Semrush, Ahrefs and Bright Data MCP servers

All three alternatives ship a hosted MCP server. The difference sits in what it takes to switch one on.

Semrush MCP

Semrush's server lives at https://mcp.semrush.com/v2/mcp, the Semrush counterpart to https://mcp.dataforseo.com/v3/mcp, speaks streamable HTTP only, and signs in by OAuth or an "Authorization: Apikey" header, per its developer docs. It names more MCP clients than DataForSEO does: Claude, ChatGPT, Cursor, VS Code, Perplexity, Lovable and Antigravity.

SEO data needs a plan carrying 50,000 API units, such as Semrush One Starter at $199 a month on monthly billing. Semrush charges no separate MCP fee, since every call draws down the same API units, and the platform holds 4.6 out of 5 across 2,328 Capterra reviews.

Pick Semrush when the team already works inside it and wants to integrate its reports with a chat window. Pick DataForSEO when the job is volume, since $199 buys 99,500 live SERP pages at DataForSEO's rate. The Semrush review and the Semrush pricing report cover the platform behind it.

Ahrefs MCP

Ahrefs includes API and MCP server access on every paid plan, starting with Lite at $129 a month, per its pricing page. Lite caps a request at 100 rows, Standard at 250 and Advanced at 500. That row cap binds on a backlink export, where DataForSEO bills $0.000036 per row returned. Ahrefs wins for a team that wants its own index and a UI to check the agent against.

Bright Data MCP

Bright Data gives 5,000 free requests a month and covers search, crawl and browser navigation across the open web. Its tools return page content, so keyword volumes and backlink counts still need a data API such as DataForSEO. Bright Data holds 4.7 out of 5 across 68 Capterra reviews. For scraping arbitrary sites, the Bright Data MCP review covers the better tool, and the web scraping tools ranking lists the rest of the field.

The DataForSEO MCP server pairs well with Surfer MCP, which scores the draft an agent writes from DataForSEO's keyword and SERP data. The MCP tools list tracks 75 confirmed servers, and the SEO tools ranking for competitive intelligence covers the platforms without one.

FAQ

Is the DataForSEO MCP server free?

The MCP server is free and open source. The API calls it makes bill against a prepaid DataForSEO balance, with a $50 minimum payment and a $1 trial credit.

Does DataForSEO have an API?

Yes. The MCP page lists eight API families, from SERP to Domain Analytics, and the server's api_request tool calls any of them. The market intelligence API ranking places DataForSEO among other data APIs.

How do I run the DataForSEO MCP server locally?

Start it with npx dataforseo-mcp-server@latest, with DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD set in the env block. Adding --mode http to npx dataforseo-mcp-server starts the streamable HTTP build on port 3000, and passing docs or request as args to npx dataforseo-mcp-server runs the CLI. That covers local development on the published build.

Who is the CEO of DataForSEO?

Nick Chernets, per the company's about page.

What are DataForSEO's competitors?

For MCP use, Semrush, Ahrefs and Bright Data each run a hosted server. For raw SERP data, SerpApi and Bright Data compete on per-request pricing.

Verdict

DataForSEO MCP suits a developer or one of the SEO professionals who knows the ropes of the underlying API. For that person it's the best of both worlds. The agent pulls live SERP and keyword data by prompt, billed at $0.0006 to $0.002 a page, with no subscription attached. Version 3's four-tool design also fixes the 42,288-token tool list that made v2 heavy to carry.

It doesn't suit a marketer who wants answers without learning which endpoint holds them. The agent reads documentation before every call, and three vendor pages still give three different connection URLs.

A small agency sits in between. The $50 top-up is a low bar, but someone on the team has to bite the bullet on field filtering and the npm version floor before handing the DataForSEO MCP server integration to account managers. Once that implementation work is done, any account manager can integrate a client's keyword research and monthly SEO reporting into a Claude chat.

Connect it to Claude, Cursor or ChatGPT

Start with DataForSEO's MCP server

The server is free and open source, and API calls bill per request from a $50 minimum top-up.

Visit DataForSEO →

May earn a commission if you sign up through this link, at no extra cost to you. Full affiliate disclosure.