AI Visibility MCP vs Google Search Console… | AllMCPs
Side-by-Side Model Context Protocol Comparison
AI Visibility MCP vs Google Search Console MCP
In-depth architectural comparison of the AI Visibility MCP and Google Search Console 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
AI Visibility MCP
Marketing · Local stdio
Quality: 44/100 (Fair) | Auth: API Key required
Google Search Console MCP
Marketing · Local stdio
Quality: 64/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose AI Visibility MCP if you need specialized Marketing tools running via a local process. Choose Google Search Console 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 AI Visibility MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: PERPLEXITY_API_KEY, OPENROUTER_API_KEY, MAX_COST_PER_CALL, MAX_DAILY_USD, LLM_MAX_OUTPUT_TOKENS, AI_VISIBILITY_SPEND_FILE.
Primary tools included: Audits 22 AI user-agents, Scores robots, schema, sitemap, llms.txt, and SPA visibility, Generates robots.txt patches and structured data.
Audit how AI sees your website. Per-bot robots.txt verdicts for 22 known AI user-agents (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bytespider, etc), Cloudflare AI-default flags, on-page schema, sitemap, llms.txt, SPA-shell detection, and cross-model brand mentions via Perplexity + OpenRouter. 0-100 score with explainable deductions; parallel competitor compare. SSRF-guarded, per-call and daily LLM spend caps. MIT, 24 tests, stdio + HTTP.
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.
Tools & Capabilities Breakdown
AI Visibility MCP Tools (6)
Audits 22 AI user-agents
Scores robots, schema, sitemap, llms.txt, and SPA visibility
Generates robots.txt patches and structured data
Checks cross-model brand mentions
Compares up to 10 domains in parallel
Enforces SSRF and LLM spending safeguards
Google Search Console MCP Tools (17)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
AI Visibility MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Search Console MCP belongs to Marketing using local stdio subprocess. Select AI Visibility MCP when you need capabilities focused on marketing and Google Search Console MCP when you require tools for marketing.