A side-by-side look at the DigestSEO mcp Geo — AI Visibility MCP Server and Qqq AI Visibility MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DigestSEO mcp Geo — AI Visibility MCP Server for marketing work as a local process; choose Qqq AI Visibility MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, SERPAPI_API_KEY.visibility.check, visibility.history, visibility.compare.check_ai_visibility, get_tool_info.Rows where the two servers differ are marked.
| Spec | Q Qqq AI Visibility MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 63/100 · Good | 76/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | OPENAI_API_KEYANTHROPIC_API_KEYGEMINI_API_KEYPERPLEXITY_API_KEYXAI_API_KEYSERPAPI_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 38 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | 2 |
| Full listing | View DigestSEO mcp Geo — AI Visibility MCP Server | View Qqq AI Visibility MCP |
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.check_ai_visibilityFree AI visibility and GEO (generative engine optimization) check for a company website by QQQ (qqq.ee). Checks whether AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended ...) may read the site, plus robots.txt, sitemap, Organization structured data, indexability and llms.txt, and returns the latest public report of brand mentions and citations in ChatGPT, Gemini and Perplexity answers when the domain has been checked before. The full AI answer check (brand visibility in live AI answers) runs on qqq.ee: the result always includes a prefilled link. Limited to a few checks per day; read-only.get_tool_infoDescribes the free QQQ AI Visibility Checker (qqq.ee): what it measures (brand mentions and website citations in ChatGPT, Gemini and Perplexity answers, AI crawler access, technical readiness for AI search / GEO), its limits, and the English and Estonian links to the web tool and full reports. No cost, no website is fetched.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.
{
"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"
}
}
}
}
{
"mcpServers": {
"qqq-ai-visibility-mcp": {
"command": "npx",
"args": [
"-y",
"qqq-ai-visibility-mcp"
]
}
}
}