GEO by VibeSEO vs Citlyze MCP
A side-by-side look at the GEO by VibeSEO and Citlyze MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GEO by VibeSEO for marketing work over a hosted endpoint; 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?
Choose GEO by VibeSEO when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 40/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | 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 | Not listed | 9 |
| Full listing | View GEO by VibeSEO | View Citlyze MCP |
Tools & capabilities
GEO by VibeSEO tools
No tool names declared yet. Check the project README from the listing page.
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.
GEO by VibeSEO
{
"mcpServers": {
"aeo-geo-by-vibeseo": {
"url": "https://geo-mcp.vibeseo.dev/mcp"
}
}
}
Citlyze MCP
{
"mcpServers": {
"citlyze-citlyze-mcp": {
"url": "https://app.citlyze.com/api/mcp"
}
}
}
Frequently asked questions
GEO by VibeSEO is categorized under Marketing and uses a remote HTTP/SSE transport. Citlyze MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick GEO by VibeSEO 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.
GEO by VibeSEO has no declared pricing — check the project's own site. 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 aeo-geo-by-vibeseo and citlyze-citlyze-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GEO by VibeSEO has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Citlyze MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.