OmniForce vs Citlyze MCP
A side-by-side look at the OmniForce and Citlyze MCP 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 Citlyze MCP for marketing over a hosted endpoint. 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 Citlyze MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CITLYZE_API_KEY. - You want tools like
get_workspace_overview, list_prompts, list_measurement_windows.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O OmniForce | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| 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 | CITLYZE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | 9 |
| Full listing | View OmniForce | View Citlyze MCP |
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.
Citlyze MCP tools 9
get_workspace_overviewWorkspace name, target brand, active prompt/location/engine counts, competitors, latest completed measurement windowlist_promptsTracked prompts with text, intent, tier, and active statelist_measurement_windowsTracking snapshots, newest firstget_visibility_overviewHeadline AI visibility metrics per brand and engineget_prompt_visibilityPer-engine and per-location metrics for one promptlist_citationsDomains cited in AI answers, with counts and sample URLslist_recommendationsOptimization recommendations, highest priority firstlist_competitor_visibilityYour brand versus tracked competitorslist_crawler_eventsDaily AI crawler visits (GPTBot, ClaudeBot, PerplexityBot, and more)
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"
}
}
}
}
Citlyze MCP
{
"mcpServers": {
"citlyze-citlyze-mcp": {
"url": "https://app.citlyze.com/api/mcp"
}
}
}
Frequently asked questions
OmniForce is categorized under Marketing and uses a local stdio subprocess. Citlyze MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick OmniForce for marketing work and Citlyze MCP 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. Citlyze MCP 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 citlyze-citlyze-mcp 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. Citlyze MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.