# @iflow-mcp/dataforseo-mcp-server [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/dataforseo/mcp-server-typescript  
**GitHub Stars:** 261  
**npm Downloads (last month):** 65  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/iflow-mcp-dataforseo-mcp-server

## Description
A Model Context Protocol (MCP) server for the DataForSEO API, enabling modular and extensible integration of DataForSEO endpoints with support for both HTTP and SSE transports.

## Tools
Capabilities this server exposes over MCP:

- **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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `DATAFORSEO_LOGIN`, `DATAFORSEO_PASSWORD` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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`:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/iflow-mcp-dataforseo-mcp-server/readme_