MCP Google Search Console

Connects Google Search Console to Claude AI, giving SEO professionals conversational access to search analytics, URL indexing status, property management, and sitemap operations across their GSC properties.

Evaluated Mar 06, 2026 (0d ago) vlatest
Homepage ↗ Repo ↗ Other google-search-console seo search-analytics indexing sitemaps python
⚙ Agent Friendliness
68
/ 100
Can an agent use this?
🔒 Security
85
/ 100
Is it safe for agents?
⚡ Reliability
77
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
70
Error Messages
50
Auth Simplicity
70
Rate Limits
65

🔒 Security

TLS Enforcement
100
Auth Strength
85
Scope Granularity
80
Dep. Hygiene
80
Secret Handling
80

Google Search Console MCP. OAuth2 with site owner verification. Site performance data — competitive intelligence. Service account or user OAuth credentials required.

⚡ Reliability

Uptime/SLA
82
Version Stability
78
Breaking Changes
72
Error Recovery
75
AF Security Reliability

Best When

An SEO professional or content team wants to ask ad-hoc questions about organic search performance without manually building GSC reports, especially for multi-property or multi-page analyses.

Avoid When

You need paid search data, real-time rank tracking, or you cannot set up Google Cloud credentials and verify GSC property ownership.

Use Cases

  • Identify top queries and landing pages by clicks/impressions with trend analysis over custom periods
  • Batch-check indexing status and crawl errors for sets of URLs
  • Submit new sitemaps and monitor their processing status
  • Compare organic performance across time periods and surface actionable SEO recommendations
  • Generate comprehensive SEO audit reports combining indexing, performance, and sitemap data

Not For

  • Non-SEO advertising data (GSC is organic search only, no paid data)
  • Users without verified GSC property ownership
  • Real-time ranking tracking (GSC data has a ~2-3 day delay)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: oauth2 service_account
OAuth: Yes Scopes: Yes

OAuth method uses client_secrets.json from Google Cloud Console for user-level auth. Service account method requires JSON key file and adding the service account email to each GSC property. Both require Search Console API enabled in GCP.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Open source tool. Google Search Console itself is free. GCP project required but no cost for typical API usage.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • GSC data has a ~2-3 day delay — agents may report stale data for very recent content
  • Domain verification must exist in GSC before the service account/OAuth user can access property data
  • Service account email must be manually added to each GSC property as a user
  • Visualizations described in docs rely on Claude's interpretation, not native chart rendering

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for MCP Google Search Console.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered