Cituna MCP vs DigestSEO mcp Geo — AI Visibility MCP Server
A side-by-side look at the Cituna 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 Cituna 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 Cituna MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CITUNA_API_KEY, CITUNA_API_URL. - You want tools like
whoami, list_brands, get_visibility.
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 | CITUNA_API_KEYCITUNA_API_URL | OPENAI_API_KEYANTHROPIC_API_KEYGEMINI_API_KEYPERPLEXITY_API_KEYXAI_API_KEYSERPAPI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 38 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 20 | 6 |
| Full listing | View Cituna MCP | View DigestSEO mcp Geo — AI Visibility MCP Server |
Tools & capabilities
Cituna MCP tools 20
whoamiConfirm the connection, plan and usage meters. Start here. For Search Console state use `gsc_status`.list_brandsBrands/domains tracked in your workspaceget_visibilityThe daily prompt × engine grid: cited or not, position, per-cell statusget_engine_answersWhat an engine actually said for a prompt, and who it cited insteadset_promptsEdit the tracked buyer questions: add, remove, enable or disable them, or replace the whole setlist_auditsScan history and a single scan's scoreslist_gapsThe fix queue, and moving items through todo → doing → donelist_keywordsKeywords with real demand, each with the stage of the page behind it. Filter `stage: "none"` for demand nothing has been written for yet. Needs Pro (the keyword dataset is a Pro feature)list_content_queueWhat AutoSEO already has in flight, so you never queue a topic twicelist_articlesThe articles AutoSEO wrote, with live URLs and when each was published, sent, edited and refreshed; and one article's stored textqueue_articleQueue a keyword so AutoSEO drafts it on the next runmark_article_publishedTell Cituna a page is live, so it stops suggesting the topic and never writes a competing page- +8 more on the listing page
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.
Cituna MCP
{
"mcpServers": {
"cituna-mcp": {
"command": "npx",
"args": [
"-y",
"cituna-mcp"
],
"env": {
"CITUNA_API_KEY": "YOUR_CITUNA_API_KEY_HERE",
"CITUNA_API_URL": "YOUR_CITUNA_API_URL_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
Cituna 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 Cituna 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.
Cituna 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 cituna-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, Cituna MCP has a quality signal of 55/100 (Good) with 0 views, 0 installs and 1 GitHub stars. DigestSEO mcp Geo — AI Visibility MCP Server has 63/100 (Good) with 4 views, 0 installs and 38 GitHub stars.