DataForSEO MCP

io.scalablyPublished by scalably.iov1.0.1Updated Nov 3, 2026

DataForSEO MCP wrapper: searchable API docs plus normalized calls to the official server. 4 tools.

VerifiedSTDIODesktop onlyWeb Search & Scraping Developer Tools

Server details

Identifier: io.scalably/dataforseo-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to scalably.io. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.scalably%2Fdataforseo-mcp.svg)](https://sourceweft.com/mcp/io.scalably%2Fdataforseo-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Wrapper around DataForSEO's official MCP server that adds a searchable docs index and normalized replies, plus a billable call to the live DataForSEO API.

What you can do: List and fetch DataForSEO API documentation sections and the docs index
Search API documentation for endpoint paths, methods, request bodies and pricing
Send authenticated requests to the live DataForSEO API with method, path or URL, and body
Return normalized JSON replies with status, summary, warnings and recovery hints, including normalized vendor task errors
When to use it: Use it when an assistant needs to look up DataForSEO SEO, SERP or keyword data endpoints and then call them, and you want documentation lookup and clearer error handling on top of the official server. If you only need raw API access, the upstream server is enough.
Requirements: Runs locally as a Node.js process via npx (npm package), desktop only. Requires a DataForSEO account and the DATAFORSEO_USERNAME (account email) and DATAFORSEO_PASSWORD (API password) environment variables. Network access to the DataForSEO API.

Before you install

api_request makes real, billable calls to DataForSEO under your account balance and rate limits; a failed paid call may be reported as ambiguous_paid_request because retrying blind could double the charge. The docs tools are free. Credentials are passed as environment variables. Do not set NODE_ENV or DATAFORSEO_PROXY_TEST_CHILD outside the test suite.

Installation

In SourceWeft

Open DataForSEO MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

DataForSEO MCP

A thin wrapper around DataForSEO's official MCP server that adds a searchable docs index and normalized errors. If you only need the raw API, install dataforseo-mcp-server directly.

Install

Claude Code:

bash

claude mcp add dataforseo -e DATAFORSEO_USERNAME=your-login -e DATAFORSEO_PASSWORD=your-password -- npx -y @scalably-io/dataforseo-mcp

claude mcp add dataforseo -e DATAFORSEO_USERNAME=your-login -e DATAFORSEO_PASSWORD=your-password -- npx -y @scalably-io/dataforseo-mcp

Codex:

bash

codex mcp add dataforseo --env DATAFORSEO_USERNAME=your-login --env DATAFORSEO_PASSWORD=your-password -- npx -y @scalably-io/dataforseo-mcp

codex mcp add dataforseo --env DATAFORSEO_USERNAME=your-login --env DATAFORSEO_PASSWORD=your-password -- npx -y @scalably-io/dataforseo-mcp

Claude Desktop: this wrapper ships on npm only (its upstream dependency makes a desktop bundle over 100 MB). Install DataForSEO's own server from https://github.com/dataforseo/mcp-server-typescript instead; the docs-search tools are the only thing you lose.

Setup

Create or open a DataForSEO account at dataforseo.com.
Read the API login (an email address) and API password from the dashboard.
api_request calls the live DataForSEO API and can incur cost per DataForSEO's own pricing; the three docs_* tools are free documentation lookups.

Tools (4)

Tool	What it does
`docs_index`	Fetch the DataForSEO API documentation index (llms.txt), optionally filtered by section
`docs_list_sections`	Return available DataForSEO API documentation section names
`docs_search`	Fetch DataForSEO API documentation from a documentation URL
`api_request`	Make an authenticated request to the DataForSEO API (method, path or url, body, and an optional noAiMode flag for the full, non AI-optimized response)

Use docs_list_sections or docs_index to pick an API family, then docs_search for the exact current endpoint path, method, request body and pricing before calling api_request.

Configuration

Variable	Required	Purpose
`DATAFORSEO_USERNAME`	yes	DataForSEO account login (email) from the dashboard
`DATAFORSEO_PASSWORD`	yes	DataForSEO account API password from the dashboard
`NODE_ENV`, `DATAFORSEO_PROXY_TEST_CHILD`	no	Test suite only: with `NODE_ENV=test` the wrapper spawns the fake child named by `DATAFORSEO_PROXY_TEST_CHILD` instead of the upstream server. Never set them in normal use

Reply shape

Every tool returns plain JSON with status (succeeded, partial, no_op), operation, summary, target, result, proof, warnings, recovery. Failures surface as a tool error whose text is <code>: <message> <hint>. api_request normalizes DataForSEO's per-task status codes (pending tasks, no-result tasks, partial failures, and vendor error codes) into that shape instead of returning DataForSEO's raw task envelope unexamined.

Limits

api_request is a real, billable call to the DataForSEO API; DataForSEO's own account balance and rate limits apply. A failed call to a paid endpoint is reported with an ambiguous_paid_request error when the outcome could not be confirmed, since retrying blind could double the charge.

Verify

Each release lists the package version and the production commit it was derived from in CHANGELOG.md; npm publishes with provenance from GitHub Actions. CI runs the tests and a clean install of the packed tarball on every push.

Privacy Policy

This server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: [email protected]. Canonical copy: https://scalably.io/connector-privacy.html

License

MIT. Copyright Scalably.

Source: README.md at commit f25681d

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts