Geode
Servers Pricing Docs Sign in Get your API key

DataForSEO MCP Server

Live Marketing & SEO Remote MCP 3 tools

SEO data API for Google keyword search volume, keyword ideas, and related keywords.

What you can do

Connect DataForSEO to your AI to pull Google keyword search volume, discover keyword ideas, and find related keywords for any location and language.

Tools

The MCP tools this server exposes to your AI. Defined from the DataForSEO API docs ↗.

keyword_search_volumeGet Google Ads monthly search volume, competition and cost-per-click for a list of keywords. Use this to gauge how much demand a set of exact keywords has.
keyword_ideasGet related keyword ideas for one or more seed keywords, each with its search volume, competition and cost-per-click. Use this to discover new keywords to target around a topic.
related_keywordsGet keywords closely related to a single seed keyword (from Google's 'searches related to' results), each with its search volume, competition and cost-per-click.

Setup

Connect in Claude

In Claude, open Settings, Connectors, Add custom connector, and paste this URL:

https://geodemcp.com/mcp/dataforseo/rpc

Click Add. Claude sends you to a GeodeMCP login screen; sign in once and DataForSEO is connected. No API key to copy.

Connect DataForSEO once in Geode, then point any client at your single endpoint. The first 100 requests are free.

What you'll need
1

Add DataForSEO in Geode

Paste your credentials once. We store them encrypted, decrypt them only in memory to make a call, and you can revoke the connection anytime.

Sign up to connect

Stored encrypted, isolated, revocable anytime.

2

Add the Geode endpoint to your client

Paste this into Claude, Cursor or any MCP client. DataForSEO shows up automatically, along with every other tool you connect.

mcp.json
// one endpoint, every connection you enabled in Geode
{
  "mcpServers": {
    "geode": {
      "url": "https://geodemcp.com/mcp/rpc",
      "headers": {
        "Authorization": "Bearer geode_sk_a1b2c3d4…"
      }
    }
  }
}
Prefer not to store credentials? Use per-request headers instead ↓
// single-tool endpoint, your token travels per request, never stored
{
  "mcpServers": {
    "dataforseo": {
      "url": "https://geodemcp.com/mcp/dataforseo/rpc",
      "headers": {
        "Authorization": "Bearer geode_sk_a1b2c3d4…",
        "X-Dataforseo-Login": "API login",
        "X-Dataforseo-Password": "API password"

      }
    }
  }
}

Report a bug or request a feature

We actively maintain this connection. Reports are tied to your Geode account, so we can follow up with you.