# Google Webtools MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/stufently/google-webtools-mcp  
**GitHub Stars:** 7  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-webtools-mcp

## Description
Google Search Console + GA4 for AI agents: properties, reports, indexing, verification, SEO.

## Tools
Capabilities this server exposes over MCP:

- **list_properties** — Starting point — see every GSC property you can access and your permission level on each.
- **get_property_details** — Check the type and permission level of one specific property.
- **add_property** — Register a new site in Search Console (verification is a separate step).
- **delete_property** — Drop a property from the authenticated account's Search Console site list. Historical data is not destroyed — the property can be added back.
- **list_sitemaps** — See which sitemaps are submitted and whether Google reports errors or warnings.
- **get_sitemap_details** — Drill into one sitemap: URL counts by content type, last download time, error and warning counts.
- **submit_sitemap** — Submit a new sitemap after publishing or moving one.
- **delete_sitemap** — Withdraw a sitemap that is stale, duplicated, or returning errors.
- **get_search_analytics** — The raw query — full control over dimensions, filters, search type, row limit, data state, aggregation. Use when the shaped tools below don't fit.
- **get_performance_summary** — "How are we doing?" — clicks, impressions, CTR, position with period-over-period comparison. Trend advice is withheld when the previous period returned no data at all.
- **compare_periods** — Compare two explicit date ranges side by side (before/after a release, seasonal comparison).
- **get_top_queries** — Top queries by clicks, each scored against the CTR benchmark for its position.
- **get_top_pages** — Top pages by clicks with the same CTR analysis.
- **get_traffic_by_device** — Split traffic across desktop, mobile, and tablet — spot device-specific problems.
- **find_quick_wins** — "Where is money left on the table?" — query/page pairs ranking well but under-clicked, and those sitting just off page 1. Each pair lands in exactly one bucket (CTR 1-3, quick gain >3 to 10, page two >10 to 20), so the counts and click estimates add up over the period you asked for.
- **find_declining_content** — Catch traffic loss while it is still recoverable — compares the current period against the previous one and reports declining pages and declining queries as two separate rankings.
- **find_ctr_opportunities** — Find pages whose CTR is far below the benchmark for their position, with per-page fix suggestions.
- **find_content_gaps** — Queries landing on the wrong page, high-impression zero-click queries, topics that need a dedicated page.
- **find_what_to_build_next** — Content planning — groups queries by user intent (question, comparison, problem, buying) into topic clusters.
- **inspect_url** — Why is this one URL not showing up? Indexing status, mobile usability, rich results — including the per-item validation issues behind a FAIL verdict.
- **batch_inspect_urls** — Same check across a list of URLs (max 50 per call).
- **check_indexing_issues** — Audit your top traffic pages for indexing failures, canonical mismatches, missing canonicals, and mobile problems. A URL the API errors on is reported as not inspected; the rest of the audit still runs.
- **analyze_query_landscape** — Understand the shape of your demand — intent mix, branded vs non-branded, position distribution.
- **find_new_queries** — Surface genuinely new and fast-rising queries by diffing this period against the previous one.
- **find_cannibalization** — Detect several of your own pages competing for the same query. The winner is the page with the most clicks, not the best average position, and queries where only one page carries real volume get no consolidation advice.
- **weekly_seo_report** — One-call weekly digest: trends, growers, decliners, quick wins, sitemap health, prioritized actions.
- **seo_health_check** — Overall A–F grade with sub-scores for traffic trend, CTR efficiency, position distribution, and sitemap health.
- **ga4_list_accounts** — See every GA4 account and property the credentials can reach.
- **ga4_list_properties** — List properties under one specific account.
- **ga4_get_property** — Inspect a property's configuration.
- **ga4_create_property** — Provision a new GA4 property. **Write operation.
- **ga4_create_data_stream** — Create a web data stream and get back its measurement ID (for installing the tag). **Write operation.
- **ga4_list_data_streams** — List a property's data streams.
- **ga4_get_data_stream** — Get one data stream's details, including its measurement ID.
- **ga4_run_report** — Any GA4 report — pick metrics, dimensions, and a date range (absolute or relative like `28daysAgo`).
- **ga4_run_realtime_report** — Who is on the site right now.
- **ga4_get_metadata** — Discover which dimensions and metrics (including custom ones) a property supports — run this before guessing metric names.
- **gsc_get_verification_token** — Get the token to place, plus method-specific instructions. Methods: `FILE`, `DNS_TXT`, `META`, `ANALYTICS`.
- **gsc_verify_site** — Complete verification once the token is in place.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Google Webtools MCP does

Google Webtools MCP MCP server exposes Google Search Console and Google Analytics 4 operations through MCP. Its Search Console coverage includes property discovery and administration, sitemap management, search analytics, URL inspection, indexing audits, query analysis, SEO reports, and site verification. GA4 tools cover account and property discovery, property configuration, data streams, standard reports, realtime reports, and metadata discovery.

The server is intended for agents that need both access to Google data and structured interpretation of that data. Search-related responses can include position-based CTR benchmarks, period comparisons, query intent classification, opportunity scoring, trend detection, recommendations, and stated limitations. Available analyses include quick wins, declining content, content gaps, cannibalization, new queries, device splits, and topic clusters.

## How it works

The Google Webtools MCP MCP server uses five Google APIs: Search Console webmasters v3 for properties, sitemaps, and search analytics; Search Console v1 for URL Inspection; the GA4 Admin API for accounts, properties, and data streams; the GA4 Data API for reports and metadata; and the Site Verification API for ownership verification.

It supports two transports: stdio by default and stateless Streamable HTTP. An in-memory TTL and LRU cache reduces repeated requests. Search analytics responses are cached for 15 minutes when the requested range ends within the last two days and for one hour for older ranges. Sitemaps and site lists have 15- and 30-minute cache periods respectively, while URL inspections are cached for one hour. A rate limiter allows 20 requests per second with a burst capacity of 30.

Use `get_search_analytics` when custom dimensions, filters, search type, row limits, data state, or aggregation are needed. Use the shaped tools for common investigations, such as comparing periods, finding underperforming pages, checking indexing, or generating a weekly SEO report. Batch URL inspection accepts up to 50 URLs per call.

## Setup and configuration

Google Cloud APIs must be enabled before use: Search Console API, Google Analytics Admin API, Google Analytics Data API, and Site Verification API. The server requests webmasters, read-only Analytics, editable Analytics, and verification-only OAuth scopes.

For automated deployments, use a Google service account with a JSON key and set `GOOGLE_APPLICATION_CREDENTIALS` to the key-file path. Add the service account email to the relevant Search Console users and permissions settings and to GA4 property access management.

For personal or local use, configure a Google OAuth 2.0 Desktop application and provide its client secrets JSON. On first launch, the server prints an authorization URL, opens a temporary local callback listener, and stores the resulting token at `~/.google-webtools-mcp/token.json`. The token is refreshed automatically.

## Tools and capabilities

The Google Webtools MCP MCP server groups its tools into these supported areas:

- Search Console properties and sitemaps, including adding or removing properties and submitting or withdrawing sitemaps.
- Search performance, including clicks, impressions, CTR, position, queries, pages, devices, and custom analytics requests.
- SEO opportunity analysis, including CTR opportunities, quick wins, declining content, content gaps, and next-topic planning.
- Indexing diagnostics, including individual URL inspection, batches of up to 50 URLs, and audits for canonical and mobile issues.
- Query analysis, including intent, branded versus non-branded demand, new queries, and competing pages.
- Reports, including weekly SEO summaries and an A–F health grade with traffic, CTR, position, and sitemap sub-scores.
- GA4 administration and reporting, including properties, data streams, reports, realtime data, and supported metric or dimension metadata.
- Site verification through token retrieval and verification completion.

Some operations change live configuration. These include adding or deleting Search Console properties, submitting or deleting sitemaps, creating GA4 properties or data streams, and completing site verification. Historical Search Console data is not destroyed when a property is removed and later added again.

_Full upstream README: https://allmcps.com/mcp/google-webtools-mcp/readme_