DigestSEO mcp Geo — AI Visibility MCP Server vs OmniForce
A side-by-side look at the DigestSEO mcp Geo — AI Visibility MCP Server and OmniForce MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
OmniForceMarketing · Local subprocess (stdio)AI-search visibility: GEO audits, tracked prompts, competitors, citations.53GoodAuth: api key requiredVerdict: choose DigestSEO mcp Geo — AI Visibility MCP Server for marketing work as a local process; choose OmniForce 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 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.
OChoose OmniForce 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:
OMNIFORCE_API_KEY, OMNIFORCE_API_BASE_URL, PORT, OMNIFORCE_ANON_DAILY_LIMIT, MCP_CTA_FOOTER. - You want tools like
omniforce_geo_scan, omniforce_get_brand, omniforce_list_prompts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O OmniForce | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 61/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | OPENAI_API_KEYANTHROPIC_API_KEYGEMINI_API_KEYPERPLEXITY_API_KEYXAI_API_KEYSERPAPI_API_KEY | OMNIFORCE_API_KEYOMNIFORCE_API_BASE_URLPORTOMNIFORCE_ANON_DAILY_LIMITMCP_CTA_FOOTER |
| Verified owner | Community listing | Community listing |
| GitHub stars | 37 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 8 |
| Full listing | View DigestSEO mcp Geo — AI Visibility MCP Server | View OmniForce |
Tools & capabilities
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.
OmniForce tools 8
omniforce_geo_scanAudit a URL's GEO/AEO readiness → evidence-based score + findings.omniforce_get_brandThe tenant's brand profile.omniforce_list_promptsQueries monitored across answer engines.omniforce_list_competitorsCompetitors tracked for the tenant.omniforce_list_snapshotsRecent radar runs (citation/visibility snapshots).omniforce_list_reportsShareable visibility reports.omniforce_accountPlan tier, included allotments, current usage, available upgrades.omniforce_upgradeCreate a hosted checkout link to upgrade the plan.
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.
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"
}
}
}
}
OmniForce
{
"mcpServers": {
"omniforce": {
"command": "npx",
"args": [
"-y",
"@omniforce/mcp"
],
"env": {
"OMNIFORCE_API_KEY": "YOUR_OMNIFORCE_API_KEY_HERE",
"OMNIFORCE_API_BASE_URL": "YOUR_OMNIFORCE_API_BASE_URL_HERE",
"PORT": "YOUR_PORT_HERE",
"OMNIFORCE_ANON_DAILY_LIMIT": "YOUR_OMNIFORCE_ANON_DAILY_LIMIT_HERE",
"MCP_CTA_FOOTER": "YOUR_MCP_CTA_FOOTER_HERE"
}
}
}
}
Frequently asked questions
DigestSEO mcp Geo — AI Visibility MCP Server is categorized under Marketing and uses a local stdio subprocess. OmniForce belongs to Marketing and uses a local stdio subprocess. Pick DigestSEO mcp Geo — AI Visibility MCP Server for marketing work and OmniForce 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.
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. OmniForce has no declared pricing — check the project's own site. 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 digestseo-mcp-geo-ai-visibility-mcp-server and omniforce as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DigestSEO mcp Geo — AI Visibility MCP Server has a quality signal of 61/100 (Good) with 3 views, 0 installs and 37 GitHub stars. OmniForce has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.