Google Search Console integration for AI agents.
Google Search Console integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Search Console tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Google Search Console actions, managed and audited.
Your user connects Google Search Console once; your agent can then inspect indexing status, manage Search Console sites and sitemaps, and query search performance analytics — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Google Search Console access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Google Search Console tools.
11 tools are generated from the published Google Search Console catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 11 tools. All published catalog entries are included in this page's server-rendered HTML.
- Searchconsole UrlInspection Index Inspect
- Index inspection.
- urlinspection
- Searchconsole UrlTestingTools MobileFriendlyTest Run
- Runs Mobile-Friendly Test for a given URL.
- urltestingtools
- Webmasters Searchanalytics Query
- Query your data with filters and parameters that you define. Returns zero or more rows grouped by the row keys that you define. You must define a date range of one or more days. When date is one of the group by values, any days without data are omitted from the result list. If you need to know which days have data, issue a broad date range query grouped by date for any metric, and see which day rows are returned.
- searchanalytics
- Webmasters Sitemaps Delete
- Deletes a sitemap from the Sitemaps report. Does not stop Google from crawling this sitemap or the URLs that were previously crawled in the deleted sitemap.
- sitemaps
- Webmasters Sitemaps Get
- Retrieves information about a specific sitemap.
- sitemaps
- Webmasters Sitemaps List
- Lists the [sitemaps-entries](/webmaster-tools/v3/sitemaps) submitted for this site, or included in the sitemap index file (if `sitemapIndex` is specified in the request).
- sitemaps
- Webmasters Sitemaps Submit
- Submits a sitemap for a site.
- sitemaps
- Webmasters Sites Add
- Adds a site to the set of the user's sites in Search Console.
- sites
- Webmasters Sites Delete
- Removes a site from the set of the user's Search Console sites.
- sites
- Webmasters Sites Get
- Retrieves information about specific site.
- sites
- Webmasters Sites List
- Lists the user's Search Console sites.
- sites
Google Search Console integration, answered
- How do AI agents use Google Search Console through Open Connector?
- Your user connects Google Search Console once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Search Console tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Google Search Console MCP server?
- Yes. Open Connector can serve Google Search Console as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Search Console actions with credentials injected server-side.
- Where do Google Search Console credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Google Search Console — keep the keys.
Open source, self-hostable, with Google Search Console credentials that never leave your infrastructure. Run it from source today.