In-depth architectural comparison of the AI Readiness 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 Readiness
Marketing · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Google Search Console MCP
Marketing · Local stdio
Quality: 64/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose AI Readiness 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 Readiness 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).
Primary tools included: AI crawler access checks, JSON-LD and metadata analysis, 0–100 score and letter grade.
Check whether a website is visible to AI search (ChatGPT, Perplexity, Claude, Google AI Overviews). Scores AI-crawler access, JSON-LD structured data, title/meta, Open Graph, sitemap, and llms.txt, with a specific fix for each gap. Dependency-free, no API keys. Install: npx -y github:epistemedeus/ai-readiness mcp.
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.
Category & Scope
Tools & Capabilities Breakdown
AI Readiness Tools (6)
AI crawler access checks
JSON-LD and metadata analysis
0–100 score and letter grade
Specific remediation guidance
Starter JSON-LD and robots.txt generation
MCP stdio transport
Google Search Console MCP Tools (17)
gsc_sites
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 Readiness 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 Readiness when you need capabilities focused on marketing and Google Search Console MCP when you require tools for marketing.