OmniForce vs AI Visibility
A side-by-side look at the OmniForce and AI Visibility 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 OmniForce for marketing work as a local process; choose AI Visibility for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose AI Visibility when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You want tools like
check_brand_visibility, check_single_query, get_visibility_score.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O OmniForce | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | OMNIFORCE_API_KEYOMNIFORCE_API_BASE_URLPORTOMNIFORCE_ANON_DAILY_LIMITMCP_CTA_FOOTER | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 10 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | 6 |
| Full listing | View OmniForce | View AI Visibility |
Tools & capabilities
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.
AI Visibility tools 6
check_brand_visibilityCheck a brand's visibility across AI platforms (ChatGPT, Perplexity, Claude, Gemini). Simulates realistic queries and analyzes mention rates, positions, sentiment, and competitor landscape.check_single_queryCheck if a brand is mentioned for a specific query on a specific AI platform. Returns mention status, position, context snippet, sentiment, and competitor mentions.get_visibility_scoreCalculate an overall AI visibility score (0-100) for a brand across all four AI platforms. Includes per-platform breakdowns and improvement recommendations.compare_brandsCompare the AI visibility of multiple brands side by side. Shows per-platform scores, overall rankings, and relative strengths.get_recommendationsGet actionable recommendations to improve a brand's AI visibility. Prioritized suggestions based on current score and industry best practices.list_platformsList all supported AI platforms with details about how each sources and presents brand information.
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.
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"
}
}
}
}
AI Visibility
{
"mcpServers": {
"sharozdawa-ai-visibility": {
"command": "npx",
"args": [
"-y",
"ai-visibility-mcp"
]
}
}
}
Frequently asked questions
OmniForce is categorized under Marketing and uses a local stdio subprocess. AI Visibility belongs to Marketing and uses a local stdio subprocess. Pick OmniForce for marketing work and AI Visibility 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.
OmniForce has no declared pricing — check the project's own site. Auth: api key required. AI Visibility has no declared pricing — check the project's own site. 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 omniforce and sharozdawa-ai-visibility as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OmniForce has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. AI Visibility has 59/100 (Good) with 2 views, 0 installs and 10 GitHub stars.