Log inSubmit server
Dataforseo MCP Server logo

Dataforseo MCP Server

by @iflow-mcp

Browse DataForSEO documentation and make authenticated API requests through MCP over stdio or Streamable HTTP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Dataforseo MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "iflow-mcp-dataforseo-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "dataforseo-mcp-server@latest"
      ],
      "env": {
        "DATAFORSEO_LOGIN": "YOUR_VALUE_HERE",
        "DATAFORSEO_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 4 tools correctly (Today).

Overview

@iflow-mcp/dataforseo-mcp-server connects MCP clients and CLI workflows to the DataForSEO API. It exposes tools for browsing API documentation, searching endpoint references, and sending authenticated requests, with stdio as the default transport and Streamable HTTP as an option. HTTP clients can authenticate through OAuth 2.0, while stdio and CLI usage use DataForSEO credentials from environment variables. Reach for it when an agent needs to discover DataForSEO endpoints and call them without a custom API wrapper.

Use cases

  • Browse DataForSEO API sections from an MCP client
  • Search endpoint documentation before constructing a request
  • Send authenticated SERP or backlink API requests
  • Run DataForSEO documentation and request workflows from a CLI

Key features

  • DataForSEO documentation index and section browsing
  • Endpoint documentation search with optional code examples
  • Authenticated API requests through MCP
  • Stdio and Streamable HTTP transports
  • OAuth 2.0 support for HTTP MCP
  • Configurable response field filtering

Tools4

What Dataforseo MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~409 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

What it can do

From the 4 tools this server returned when we ran it; 4 declare their own safety hints.

Makes network requests · 4Read-only tools · 4
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age546 days
Maintainers1

Observed 2026-11-09 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14h ago via OSV.dev · dataforseo-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars261Stargazers on the source repository.
npm downloads65Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.

How Dataforseo MCP Server works

What @iflow-mcp/dataforseo-mcp-server does

@iflow-mcp/dataforseo-mcp-server gives LLM agents access to DataForSEO API documentation and authenticated API requests. It can retrieve the documentation index, list available documentation sections, search endpoint documentation, and send requests to DataForSEO API paths.

The package also includes a CLI using the same underlying implementations as the MCP server. CLI commands cover documentation indexing, documentation searches, and arbitrary authenticated API requests. The default request path uses DataForSEO's .ai variant; callers can select the standard path instead.

How it works

Running the package without a CLI command starts an MCP server over stdio. Passing --mode http starts a Streamable HTTP server, exposing MCP endpoints at /mcp and /http; the default port is 3000 and can be changed with PORT.

HTTP mode exposes OAuth 2.0 Protected Resource metadata so compatible clients can discover the authorization server and send Bearer tokens. Basic authentication and environment-provided credentials are also supported, with HTTP authentication checked in a defined priority order. Stdio and CLI modes use the DataForSEO login and password from the environment.

Documentation results are cached for 24 hours. The cache location follows the operating system's normal cache directory and can be overridden for MCP startup or CLI documentation commands. API responses are returned as parsed JSON when possible.

Setup and configuration

Install and run the published package with npx:

Terminal
npx dataforseo-mcp-server@latest

Set DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD before using stdio or CLI mode. DATAFORSEO_USERNAME is accepted as an alias for the login variable. For HTTP mode, clients can connect to the hosted endpoint at https://mcp.dataforseo.com/v3/mcp, or to a local server such as http://localhost:3000/mcp.

MCP clients that use an mcpServers configuration can start the package with a command for stdio or connect by URL for HTTP. The server also accepts --docs-cache-dir and --configuration startup options. Field filtering can be configured with a JSON file through FIELD_CONFIG_PATH, inline JSON through FIELD_CONFIG_JSON, or the --configuration option. Filters are keyed by API endpoint path and can reduce returned responses to selected fields.

Tools and capabilities

  • docs_index retrieves the API documentation index and can filter it by section.
  • docs_list_sections returns available documentation section names.
  • docs_search fetches documentation for a documentation URL or path, with an option to include code examples.
  • api_request sends an authenticated API request with a JSON object or array as its body.
  • CLI docs commands support indexes, section lists, and endpoint searches.
  • CLI request supports HTTP methods, API paths, JSON bodies, and repeated --param options.

Limitations and notes

The --param option is available only in the CLI; MCP callers pass request data through the tool input. The HTTP server's metadata URLs may need TRUST_PROXY=true when deployed behind a reverse proxy so generated URLs use HTTPS. Field configuration can trim API responses, so the returned data may contain only the fields selected for an endpoint.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dataforseo MCP Server

@iflow-mcp/dataforseo-mcp-server is an MCP server that connects AI agents to the DataForSEO API. Its main tools retrieve documentation indexes, list sections, search endpoint documentation, and make authenticated API requests. It runs over stdio by default and also supports Streamable HTTP with OAuth authentication.

Run `npx dataforseo-mcp-server@latest` to start the default stdio server. Set `DATAFORSEO_LOGIN` and `DATAFORSEO_PASSWORD` for stdio or CLI authentication. To use HTTP, run `npx dataforseo-mcp-server@latest --mode http`.

Yes, it works with Cursor through an `mcpServers` configuration. Connect Cursor to the hosted URL, a local HTTP URL, or start the package with the `command` configuration and DataForSEO credential environment variables.

Use the `docs_search` tool with a DataForSEO documentation URL or path. The server also provides `docs_index` for browsing the full index or filtering by section and `docs_list_sections` for discovering available section names.

Use the `api_request` tool with the HTTP method, API path, and request data. Requests use `.ai` paths by default; set `noAiMode` to `true` to use the standard path. Authentication comes from HTTP authorization or configured DataForSEO credentials.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDataforseo MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/iflow-mcp-dataforseo-mcp-server?style=directory)](https://allmcps.com/mcp/iflow-mcp-dataforseo-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/iflow-mcp-dataforseo-mcp-server"><img src="https://allmcps.com/api/badge/iflow-mcp-dataforseo-mcp-server?style=directory" alt="Dataforseo MCP Server on AllMCPs" /></a>