Skip to content

Connectors · Marketing & media

Google Search Console MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Search Console and the rest of your systems. It gives your agent 10 Google Search Console actions (6 reads, 2 writes and 2 that wait for a confirmation) and holds the Google Search Console credential itself, so the agent never does. It paces Google Search Console's limits and records every call. Connecting Google Search Console needs your own Google Search Console OAuth app and one admin sign-in.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "google_search_console.sites.list",  intent: "check which Google Search Console account is connected"}# List Search Console sites · read · 1 upstream call
  • 10actionsin one signed file
  • 6readlook, never change
  • 2writecreate and update
  • 2wait for a yesdestructive, confirmed first

Set up

Connect Google Search Console in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Google Search Console.

    OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Search Console, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.

    Before the first sign-in, Google Search Console needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Search Console app to lend you.

    • access_tokenAccess token from one sign-in with your own OAuth app
    • refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
    • client_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Google Search Console API…
    • client_secretGoogle OAuth client secret
    account { op: "connections.requirements", service: "google_search_console" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "google_search_console.sites.list" }# list search console sites · read · 1 upstream callcheck { action: "google_search_console.sites.add", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Search Console at a glance

Sign-in
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Search Console, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide
access_tokenrefresh_tokenclient_idclient_secret
Limits we pace to
1,200 calls a minute, per connection
API covered
Search Console API v1 / webmasters v3 (Discovery revision 20261021)searchconsole.googleapis.com
Built from
Google Search Console's documentation, read 22 October 2026searchconsole.googleapis.comdevelopers.google.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
6 of 6 reads, for up to an hour; a write clears what it affects
Shared entities
1, so ask can line Google Search Console up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Google Search Console.

10 actions in 4 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 6readlook, never change
  • 2writecreate and update
  • 2destructivewait for a confirmation
  1. Sitemaps

    4

    2 read · 1 write · 1 destructive

    List sitemaps for a site · Submit a sitemap · Get a sitemap · Delete a sitemap

  2. Sites

    4

    2 read · 1 write · 1 destructive

    List Search Console sites · Add a site to Search Console · Get a Search Console site · Remove a site from Search Console

  3. Search analytics

    1

    1 read · 0 write · 0 destructive

    Query search analytics (clicks, impressions, CTR, position)

  4. URL inspection

    1

    1 read · 0 write · 0 destructive

    Inspect a URL's index status

Top actions

The Google Search Console API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 4 of Google Search Console's 4 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
google_search_console.sites.listList Search Console sitesLists the user's Search Console sites.readcontent.site.list16 connectors
google_search_console.sites.addAdd a site to Search ConsoleAdds a site to the set of the user's sites in Search Console.writecontent.site.create12 connectors
google_search_console.sites.deleteRemove a site from Search ConsoleRemoves a site from the set of the user's Search Console sites.destructivecontent.site.delete13 connectors
google_search_console.sitemaps.listList sitemaps for a siteLists the [sitemaps-entries](/webmaster-tools/v3/sitemaps) submitted for this site, or included in the sitemap index file (if `sitemapIndex` is specified in…readthis connector
google_search_console.sitemaps.submitSubmit a sitemapSubmits a sitemap for a site.writethis connector
google_search_console.search_analytics.queryQuery search analytics (clicks, impressions, CTR, position)Query your data with filters and parameters that you define.readthis connector

Try it

Prompts to paste into Claude.

Each one names the Google Search Console actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List Search Console sites in Google Search Console and tell me what stands out.

    callsgoogle_search_console.sites.list

  2. Writewrite

    Add a site to Search Console in Google Search Console. Show me exactly what you will send before you save it.

    callsgoogle_search_console.sites.add

Governance for Google Search Console

Destructive actions wait for a yes.

2 Google Search Console actions are destructive. These are all of them:

  • Remove a site from Search Consolegoogle_search_console.sites.delete
  • Delete a sitemapgoogle_search_console.sitemaps.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dogoogle_search_console.sites.deleteconfirm_policy: human

Remove a site from Search Console?

intent: the user asked me to remove a site from Search Console

run suspended · waiting for a named person · key google-search-console-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "google-search-console-agent",  allowed_actions: ["google_search_console.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "google_search_console.sites.delete", approver: "[email protected]" },    { match: "google_search_console.sitemaps.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Google Search Console only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Google Search Console costs on actionlake.

Every Google Search Console action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Search Console refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 10 Google Search Console actions
  • 10actions pageeach page of a long list is one call
  • 6reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Search Console action.

10 actions by area: the id your agent calls, what it does, and its effect.

Sitemaps4
  • google_search_console.sitemaps.deleteDelete a sitemapdestructive
  • google_search_console.sitemaps.getGet a sitemapread
  • google_search_console.sitemaps.listList sitemaps for a siteread
  • google_search_console.sitemaps.submitSubmit a sitemapwrite
Sites4
  • google_search_console.sites.addAdd a site to Search Consolewrite
  • google_search_console.sites.deleteRemove a site from Search Consoledestructive
  • google_search_console.sites.getGet a Search Console siteread
  • google_search_console.sites.listList Search Console sitesread
Search analytics1
  • google_search_console.search_analytics.queryQuery search analytics (clicks, impressions, CTR, position)read
URL inspection1
  • google_search_console.url_inspection.inspectInspect a URL's index statusread

Questions

The Google Search Console MCP server, answered.

Is there a Google Search Console MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 10 Google Search Console actions across sitemaps, sites, search analytics and URL inspection, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Search Console.

What do I need to connect Google Search Console?

Your own Google Search Console OAuth app, registered with Google Search Console (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Search Console app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "google_search_console" } lists exactly what to paste.

Can an AI agent delete or change things in Google Search Console?

Only if its key allows it, and only with an explicit confirmation. 2 Google Search Console actions are destructive, including remove a site from Search Console and delete a sitemap. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Google Search Console API limit?

actionlake paces every call to the limits in the Google Search Console service file: 1,200 calls a minute per connection. Repeated reads are answered from cache (6 Google Search Console actions can be), which never reaches Google Search Console.

What does a Google Search Console action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (10 Google Search Console actions page). Cache hits, searches, dry runs and calls Google Search Console refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Google Search Console API does it cover?

The Search Console API v1 / webmasters v3 (Discovery revision 20261021) at searchconsole.googleapis.com. It is built from Google Search Console's documentation as read on 22 October 2026. 10 actions in 4 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Search Console data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Search Console credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Google Search Console today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.