Access, auth, and limits
DataForSEO MCP uses Basic authentication with your DataForSEO login and the dedicated API password generated in your account dashboard (separate from the account login password for security). Every MCP call consumes from the same pay-as-you-go credit balance as direct REST API calls. No separate MCP-tier pricing, no MCP-only minimum, no MCP-exclusive endpoints. The $50 minimum top-up applies to total account credit, not per-surface.
Setup takes minutes: generate the API password in the dashboard, paste the credentials into your MCP client config, point at the DataForSEO MCP server URL. Rate limits surface via standard X-RateLimit-Limit and X-RateLimit-Remaining HTTP headers; contact support for increases. A sandbox environment is documented for testing MCP calls without burning real credits, which is rare among SEO MCP servers and useful when prototyping agent workflows.
Where it works and what to build
Per the DataForSEO MCP pitch, supported clients include Claude (Desktop and Web), ChatGPT (via custom connectors), Cursor, Codex, Windsurf, Cline, plus n8n for low-code automation. Gemini is technically API-only since Gemini chat lacks a native MCP client, but the DataForSEO REST API is straightforward to call from a Gemini Code Assist context. The wire-once-multi-client framing matters because DataForSEO covers 11 distinct API categories (SERP, AI Optimization, Keywords Data, Domain Analytics, Labs, Backlinks, OnPage, Content Analysis, Merchant, App Data, Business Data). Wiring all of that into a custom integration per LLM client would be weeks of work; MCP collapses it to one wire-up.
Real workflows worth running once MCP is connected: ask Claude where your 200 target keywords rank this week (SERP API routes the call and returns positions, AI Overview citations, and SERP-feature presence in a single response), drop a topic and have the agent pull Keyword Ideas + Search Intent + top-10 results from MCP so it writes a brief based on what page 1 is doing today rather than what training data thinks page 1 looks like, trigger a backlink delta pull on every deploy via n8n + MCP and catch toxic spikes inside the sprint instead of next quarter's audit, or expose SERP/Keywords/Labs/OnPage/Backlinks/Business Data/Domain Analytics through one protocol so Claude, ChatGPT, Cursor, and Gemini all read the same data without parallel integration work.
Which AI clients can use DataForSEO MCP?
Not every AI assistant supports MCP natively. Per-client picture for DataForSEO:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Connect via the DataForSEO MCP URL in Claude Desktop settings; uses Basic auth with your API password. |
| Claude Code | Native MCP | — |
| ChatGPT | Via connectors | Works via ChatGPT custom connectors. Per Nick Chernets (DataForSEO founder), explicitly supported. |
| Cursor | Native MCP | — |
| Codex | Native MCP | — |
| Windsurf | Native MCP | — |
| Cline | Native MCP | — |
| Gemini | API-only (custom code) | Gemini chat has no native MCP client; call the REST API directly from Gemini Code Assist or custom code. |
| n8n | Native MCP | Per DataForSEO MCP pitch, n8n is explicitly supported via the MCP HTTP node. |
How to connect DataForSEO MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"dataforseo": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"DATAFORSEO_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://github.com/dataforseo/mcp-server-typescript
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: github.com/dataforseo/mcp-server-typescript.
Does DataForSEO MCP cost extra?
DataForSEO ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your DataForSEO plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
DataForSEO also publishes a REST API
DataForSEO is API-first: you pay per API call, no monthly subscription required.
What you can do with DataForSEO from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What keywords moved this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe DataForSEO data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's DataForSEO account
- Multi-account workflows without context-switching the DataForSEO UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage DataForSEO data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production DataForSEO safe
Limits and gotchas
- Official MCP server — published by DataForSEO themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying DataForSEO API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Score: 8/10 on MCP-readiness. DataForSEO ships an official MCP server exposing 7+ APIs through one protocol with multi-client support (Claude, ChatGPT, Cursor, Gemini, n8n per the vendor's own framing). For LLM agents that need live SEO data instead of training-data SERPs, this is the clearest first-party MCP story in the SEO data category. The score isn't a 10 because pay-as-you-go credit consumption means even casual MCP calls draw down the same $50-minimum budget as direct API calls, and Gemini support is API-only rather than native MCP.
Solid agent foundation with official MCP and documented API. DataForSEO's MCP server and ChatGPT integration provide direct workflows, though the lack of OpenAPI specs and Claude support limits flexibility for multi-LLM agent stacks. Node SDK availability helps but webhooks and structured outputs would unlock more autonomous use cases.
Scored 2026-06-07 by Joonas (TMB).
DataForSEO MCP & API FAQ
Is the DataForSEO MCP server official?+
Can I use the DataForSEO MCP with Cursor or Codex?+
Does DataForSEO have a public API?+
Which LLMs does DataForSEO integrate with directly?+
Sources
- DataForSEO official site: https://dataforseo.com/
- MCP server page: https://github.com/dataforseo/mcp-server-typescript
- API docs: https://docs.dataforseo.com/v3/
- Pricing source: https://dataforseo.com/pricing (verified 2026-06-07)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.