Citlyze MCP vs Cituna MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Citlyze MCP vs Cituna MCP
In-depth architectural comparison of the Citlyze MCP and Cituna MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Citlyze MCP
Marketing · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Cituna MCP
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Citlyze MCP if you need specialized Marketing tools running via a local process. Choose Cituna MCP if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Citlyze MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Track how your brand shows up in AI search with Citlyze: visibility scores, tracked prompts, citations, competitor comparison, recommendations, and AI crawler analytics across ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews. Read-only hosted endpoint at app.citlyze.com/api/mcp.
Track how 6 AI engines cite your brand, daily, with live Google Search Console.
Citlyze MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Cituna MCP belongs to Marketing using local stdio subprocess. Select Citlyze MCP when you need capabilities focused on marketing and Cituna MCP when you require tools for marketing.
Domains cited in AI answers, with counts and sample URLs
list_recommendations
Optimization recommendations, highest priority first
list_competitor_visibility
Your brand versus tracked competitors
list_crawler_events
Daily AI crawler visits (GPTBot, ClaudeBot, PerplexityBot, and more)
Cituna MCP Tools (12)
whoami
Confirm the connection, plan and usage meters. Start here. For Search Console state use `gsc_status`.
list_brands
Brands/domains tracked in your workspace
get_visibility
The daily prompt × engine grid: cited or not, position, per-cell status
get_engine_answers
What an engine actually said for a prompt, and who it cited instead
list_audits
Scan history and a single scan's scores
list_gaps
The fix queue, and moving items through todo → doing → done
list_keywords
Keywords 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_queue
What AutoSEO already has in flight, so you never queue a topic twice
queue_article
Queue a keyword so AutoSEO drafts it on the next run
mark_article_published
Tell Cituna a page is live, so it stops suggesting the topic and never writes a competing page