Skip to main content
Glama
io.scalably/dataforseo-mcp

io.scalably/dataforseo-mcp

Official
by scalably-io

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:

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

Codex:

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.

Related MCP server: novada-mcp

Setup

  1. Create or open a DataForSEO account at dataforseo.com.

  2. Read the API login (an email address) and API password from the dashboard.

  3. 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: hello@scalably.io. Canonical copy: https://scalably.io/connector-privacy.html

License

MIT. Copyright Scalably.

Available Tools

4 tools
api_requestAPI RequestB

Make an authenticated request to the DataForSEO API

Inputs: method (required), url, data, path, +1 more.

docs_indexDocs IndexB
Read-onlyIdempotent

Fetch the DataForSEO API documentation index (llms.txt), optionally filtered by section

Inputs: section.

docs_list_sectionsDocs List SectionsA
Read-onlyIdempotent

Return available DataForSEO API documentation section names

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct: api_request handles API calls, docs_search fetches specific documentation pages, docs_index retrieves the documentation index, and docs_list_sections lists section names. However, docs_search and docs_index could be confused since both retrieve documentation-related content, though their purposes differ enough to avoid significant ambiguity.

    Naming Consistency3/5

    Three tools share a consistent 'docs_' prefix with verb-noun style (docs_search, docs_index, docs_list_sections), but api_request breaks the pattern and uses a noun-noun construction. The naming is readable but not fully uniform, mixing conventions.

    Tool Count5/5

    Four tools is an ideal size for a focused server that combines documentation retrieval with API request execution. Each tool has a clear purpose, and the count feels neither sparse nor bloated for the server's stated scope.

    Completeness5/5

    The tool set covers the full workflow: discovering available sections (docs_list_sections), browsing the index (docs_index), fetching specific documentation (docs_search), and making authenticated API requests (api_request). No obvious dead ends or missing core operations are apparent for a documentation and API helper server.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      B
      maintenance
      Hosted MCP server for 3926 structured public web-data tools across 488 platform groups, returning clean JSON for search, maps, commerce, social, and finance.
      14
      500
      252 npm
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Model Context Protocol (MCP) server implementation for DataForSEO, enabling AI assistants to interact with selected DataForSEO APIs and obtain SEO data through a standardized interface.
      89
      10,352 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.
      1
      MIT