In-depth architectural comparison of the Google Search Console 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
Google Search Console Mcp
Marketing · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Cituna Mcp
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Google Search Console 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 Google Search Console Mcp when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN.
Google Search Console MCP server: query performance data, inspect URLs, check indexing, and generate brandable HTML SEO audit reports with a 30/60/90-day roadmap. Read-only OAuth scope, installable via uvx mcp-google-search-console.
Track how 6 AI engines cite your brand, daily, with live Google Search Console.
Google Search Console Mcp is categorized under Marketing and uses a local stdio subprocess. In contrast, Cituna Mcp belongs to Marketing using local stdio subprocess. Select Google Search Console Mcp when you need capabilities focused on marketing and Cituna Mcp when you require tools for marketing.
Generate a complete HTML audit report for a date range
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