← All integrations

Google Search Console MCP server

10 operations0 webhooks

Query search performance and inspect indexing, mobile usability and rich results through the Google Search Console API.

Try Google Search Console with your agent

Connect Google Search Console, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Google Search Console on my account, then run one read-only example and show me the result.

Runs once, when you ask

Google Search Console tools and triggers

Tools are what your agent can do in Google Search Console through Corsair's MCP server. Triggers are the Google Search Console events a routine can start from.

Sitemaps

  • DeleteDestructive

    Remove a sitemap from the property's Sitemaps report. Google may still crawl the sitemap and the URLs it already found

    sitemaps.delete

  • GetRead-only

    Read one submitted sitemap

    sitemaps.get

  • ListRead-only

    List the sitemaps submitted for a property, with their errors and warnings

    sitemaps.list

  • SubmitWrite

    Submit a sitemap URL, which asks Google to fetch it. Sending one already listed refreshes its status

    sitemaps.submit

Sites

  • AddWrite

    Add a property the account already controls to the API's property list. It does not verify ownership

    sites.add

  • DeleteDestructive

    Remove a property from this account's Search Console property list. Other owners keep it, and it can usually be re-added without verifying again

    sites.delete

  • GetRead-only

    Read one property and the permission level on it

    sites.get

  • ListRead-only

    List the properties the credentials can reach, with the permission level on each

    sites.list

Searchanalytics

  • QueryRead-only

    Query search traffic: clicks, impressions, CTR and position, grouped by date, query, page, country, device or another dimension

    searchanalytics.query

Url Inspection

  • InspectRead-only

    Inspect one URL: whether Google indexed it, the canonical it chose, and any mobile-usability, rich-result or AMP issues

    urlInspection.inspect

Connect Google Search Console to Claude, ChatGPT or Cursor

  1. 1

    Connect Google Search Console in Corsair

    Sign in to Google Search Console once in Corsair. Corsair stores the credential encrypted and makes the Google Search Console API calls for your agent, so it never goes into a prompt or a config file. Connect Google Search Console

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Google Search Console. On a ChatGPT personal plan, connect Google Search Console here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Google Search Console's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/googlesearchconsole, add the Google Search Console plugin, and connect with OAuth. Then call methods like corsair.googlesearchconsole.api.searchanalytics.query() from your app. Corsair stores tokens, and keeps each tenant isolated.

Yes. Google Search Console needs an OAuth app with scopes that match what you automate. Register the app in Google Search Console, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit Google Search Console, GitHub, Notion, Stripe, and the rest. Trigger Google Search Console from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for query search performance and inspect indexing, mobile usability and rich results through the Google Search Console API. Common builds include sync jobs, admin tooling, and agents that call Google Search Console APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Google Search Console API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/googlesearchconsole in the open repo. When Google Search Console ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Google Search Console data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Google Search Console data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Google Search Console on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Google Search Console operations. You can change a link's mode at hub.corsair.dev/me.