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.
- Auth flow: MCP servers usually inherit the underlying API auth method (unknown). Expect to configure that on first install.
- 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
Solid agent fit with official MCP and documented API. DataForSEO's official MCP server and public API docs make it straightforward to integrate into Claude/Cursor workflows, though the missing OpenAPI spec and lack of native Claude integration mean you'll do some manual setup. The absence of webhooks and structured outputs limits real-time automation and response formatting options.
Scored 2026-05-19 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 (scraped 2026-05-19)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

