Connect Search Console via MCP

Reads cover Search Analytics, cannibalisation, query clustering, losses and gains, search types, freshness and sitemap health. This source cannot write. gsc_inspect_url reads inspection status; it does not request indexing. There is no confirm path on Search Console because there is no write tool.

More prompts live on the Search Console MCP Server page. gsc_list_sitemaps and gsc_get_sitemap_health read submitted sitemaps. gsc_inspect_url and gsc_bulk_inspect_urls read inspection status. Do not expect a sitemap submit or an index request through this URL. If a prompt asks the assistant to request indexing, the catalogue has no tool for it.

No. Official Google Ads MCP is three read-only Ads API tools you run yourself, with no Google-hosted URL. Search Console is a different API. This gateway ships both, plus GA4, as separate live sources on one URL, each with its own ticked-account allowlist. That join is the point of a hosted gateway.

Google's Ads MCP developer guide is pipx or your own Cloud Run, developer token plus GCP, tools list_accessible_customers, search and get_resource_metadata. None of those are Search Analytics. A paid-versus-organic question needs google_ads_get_search_terms and gsc_query_search_analytics in one thread. Official Ads MCP cannot do that join. See Google Ads and GA4 in one MCP.

Meta official mcp.facebook.com/ads is Meta only. TikTok official is TikTok only. Neither includes Search Console. There is no X Ads on this gateway. Microsoft Advertising is soon: OAuth exists, tools do not. Organic next to paid is a live-source problem, not an official-ads-MCP problem.

Connect both sources, tick the Ads customer and the Search Console property separately, then ask a question that names both. Paid search terms live in Google Ads; organic queries live in Search Console. The assistant calls google_ads_* and gsc_* in one thread. Official Google Ads MCP cannot do that join because it has no GSC tools.

A worked ask: which paid search terms overlap organic queries we already rank for. Map that to google_ads_get_search_terms then gsc_query_search_analytics. If only one source is ticked, the other call is refused. Ticking is human-only. See What a ticked-account allowlist is and the one URL article.

GA4 is the third Google source if checkout events belong in the same question. Ticking a GA4 property is a third picker. Writes, if any, still live on Google Ads paid plans, preview then confirm, never on Search Console. Pricing does not add a GSC write; this source cannot write.

Do not use this source when you need to submit a sitemap or request indexing, when the property is not ticked, when you only wanted Google's official Ads MCP, or when you need X Ads or Microsoft Advertising tools. This source is read only. Connecting the Google identity is not enough.

• You need to submit a sitemap or inspect-and-index as a write. This source is read only. gsc_inspect_url reads inspection status; it does not request indexing.
• The property is not ticked. Connecting the Google identity is not enough.
• You only wanted Google's official Ads MCP. That server does not include Search Console.
• You need X Ads or Microsoft Advertising tools. This gateway does not ship them.

If the job is Ads-only GAQL on a machine you operate, use official Google Ads MCP. If the job is organic queries next to paid terms, one hosted URL is the other shape. There is no X Ads. Microsoft Advertising is soon, with no tools. Live sources stay Meta Ads, Google Ads, TikTok Ads, Pinterest Ads, GA4 and Search Console.