DataForSEO MCP vs DigestSEO mcp Geo — AI Visibility MCP Server
A side-by-side look at the DataForSEO MCP and DigestSEO mcp Geo — AI Visibility MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DataForSEO MCP for marketing work as a local process; choose DigestSEO mcp Geo — AI Visibility MCP Server for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DataForSEO MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DATAFORSEO_USERNAME, DATAFORSEO_PASSWORD. - You want tools like
docs_index, docs_list_sections, docs_search.
Choose DigestSEO mcp Geo — AI Visibility MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, SERPAPI_API_KEY. - You want tools like
visibility.check, visibility.history, visibility.compare.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 55/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | DATAFORSEO_USERNAMEDATAFORSEO_PASSWORD | OPENAI_API_KEYANTHROPIC_API_KEYGEMINI_API_KEYPERPLEXITY_API_KEYXAI_API_KEYSERPAPI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 38 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 4 | 6 |
| Full listing | View DataForSEO MCP | View DigestSEO mcp Geo — AI Visibility MCP Server |
Tools & capabilities
DataForSEO MCP tools 4
docs_indexFetch the DataForSEO API documentation index (llms.txt), optionally filtered by sectiondocs_list_sectionsReturn available DataForSEO API documentation section namesdocs_searchFetch DataForSEO API documentation from a documentation URLapi_requestMake an authenticated request to the DataForSEO API (method, path or url, body, and an optional noAiMode flag for the full, non AI-optimized response)
DigestSEO mcp Geo — AI Visibility MCP Server tools 6
visibility.checkLatest AI visibility snapshot across all configured engines for a tracked brand, with per-engine scores, winning prompts, and losing prompts.visibility.historyTime-series history of overall and per-engine visibility, bucketed daily or weekly.visibility.compareShare-of-voice comparison against competitor domains, with prompts you win and prompts they win.visibility.citationsThe actual citation events — prompt, engine, response excerpt, citation type, brand URL when present.visibility.content_gapsPrioritized Claude-Haiku-generated content recommendations targeting your losing prompts.visibility.refreshManually trigger a fresh scan across every engine whose API key is set.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
DataForSEO MCP
{
"mcpServers": {
"dataforseo-mcp": {
"command": "npx",
"args": [
"-y",
"@scalably-io/dataforseo-mcp"
],
"env": {
"DATAFORSEO_USERNAME": "YOUR_DATAFORSEO_USERNAME_HERE",
"DATAFORSEO_PASSWORD": "YOUR_DATAFORSEO_PASSWORD_HERE"
}
}
}
}
DigestSEO mcp Geo — AI Visibility MCP Server
{
"mcpServers": {
"digestseo-mcp-geo-ai-visibility-mcp-server": {
"command": "npx",
"args": [
"-y",
"@digestseo/mcp-geo"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
"SERPAPI_API_KEY": "YOUR_SERPAPI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
DataForSEO MCP is categorized under Marketing and uses a local stdio subprocess. DigestSEO mcp Geo — AI Visibility MCP Server belongs to Marketing and uses a local stdio subprocess. Pick DataForSEO MCP for marketing work and DigestSEO mcp Geo — AI Visibility MCP Server for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
DataForSEO MCP has no declared pricing — check the project's own site. DigestSEO mcp Geo — AI Visibility MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dataforseo-mcp and digestseo-mcp-geo-ai-visibility-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DataForSEO MCP has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. DigestSEO mcp Geo — AI Visibility MCP Server has 63/100 (Good) with 4 views, 0 installs and 38 GitHub stars.