Google Webtools MCP

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.