How to Connect Google Search Console to Claude (Step by Step, Free)

It’s Monday morning, and your manager asks a simple question: which blog posts lost traffic last month? So you open Search Console, click Performance, add a date filter, add a page filter, export to a spreadsheet, and start sorting. Forty minutes later, you have one answer. Now imagine typing that same question to Claude and getting the answer in seconds. That is what a Google Search Console MCP setup does. You connect Claude to your own Search Console data once, then just ask.

This guide shows the full GSC MCP setup, step by step, without paying for anything. It works for students learning SEO, site owners, and software house teams who report on website performance.

What Is a Google Search Console MCP?

MCP stands for Model Context Protocol. It’s a standard way for AI apps like Claude to connect to outside tools and data.

A Google Search Console MCP server is a small program that runs on your computer. When you ask Claude about your site, Claude talks to the program, the program fetches the numbers from Google’s Search Console API, and Claude explains them in plain language.

One thing to know up front: the servers I found are open-source projects built by the community, not something Google publishes. Examples include suganthan-gsc-mcp on npm, mcp-gsc on GitHub, and mcp-google-search-console on PyPI. The setup below uses the first one, and the others follow a similar pattern with their own commands.

What Can You Do With Search Console and Claude?

The exact tools depend on the server you pick. The one used in this guide ships with 29 tools. Here are the ones most beginners will use first:

Because Claude understands context, you can keep going: “Show only the ones with more than 1,000 impressions,” or “Which of those are blog posts?”

What You Need Before You Start

• A Google account with at least one verified property in Search Console.

• A free Google Cloud account, used to create access credentials.

• The Claude Desktop app. The guide I followed says the free plan works, but plan limits change, so check Claude’s current docs.

• Node.js installed, because the server starts with an npx command.

• About 15 minutes. The server, the Google Cloud project, and the Search Console API are all free.

GSC MCP Setup: Step by Step

You can sign in in two ways: OAuth or a service account. OAuth is easier and best for personal use, so we’ll use that. A service account suits automation and agencies managing many sites.

Step 1: Create a Google Cloud project.

• Go to console.cloud.google.com and open the project dropdown.

• Click New Project, name it something like “GSC MCP,” and click Create.

Step 2: Enable the Search Console API

• Search for “Google Search Console API” in the top bar and open it.

• Click Enable.

• Optional: also enable the Web Search Indexing API if you want Claude to submit URLs for indexing.

Step 3: Create OAuth credentials

• Open APIs & Services, then Credentials, then Create Credentials and OAuth Client ID.

• If asked to set up a consent screen, choose External, enter an app name and your email, and save.

• Choose Desktop app as the application type and click Create.

• Click Download JSON and save the file somewhere safe, for example, your home folder.

Step 4: Add the server to Claude Desktop.

In Claude Desktop, open Settings, go to the Developer tab, and click Edit Config. Add this block:

{

  "mcpServers": {

    "gsc": {

      "command": "npx",

      "args": ["-y", "suganthan-gsc-mcp"],

      "env": {

        "GSC_AUTH_MODE": "oauth",

        "GSC_OAUTH_SECRETS_FILE": "/path/to/gsc-oauth-secrets.json",

        "GSC_SITE_URL": "sc-domain:yourdomain.com"

      }

    }

  }

}

Replace the file path with the location of your downloaded JSON and the domain with your own. If you already have other servers in this file, add this one alongside them instead of replacing them. Save, then fully restart Claude Desktop.

Step 5: Sign in to Google.

Ask Claude any question about your site. A browser window opens for Google sign-in. Approve the permissions, and you’ll see an “Authentication successful” message. The token is cached, so you won’t repeat this. Back in Claude’s Developer settings, the server should show as running.

The Mistake That Breaks Most Setups

Search Console has two property types, and the format in GSC_SITE_URL must match:

Get this wrong, and everything looks fine while nothing works. Check your property selector in Search Console first.

Using It With Claude Code

If you prefer the terminal, register the server with one command:

claude mcp add gsc -- npx -y suganthan-gsc-mcp

Then set the same environment variables as above. Other servers, such as mcp-gsc, use a JSON entry in your MCP config pointing to a Python script instead.

How to Automate SEO Reports With Claude

This is where the setup pays off. To automate SEO reports, give Claude one prompt that covers your routine checks:

Generate a performance report for the last 28 days. Include a site snapshot, any alerts, quick wins, pages that lost traffic, and three recommended actions.

The server used here can save the result as a markdown file, so you can attach it to an email or archive it for weekly reviews. A fair expectation: this removes the clicking and exporting, but you still start each report by asking. Scheduling it to run on its own needs extra tooling beyond this setup.

If you manage several client sites, the same server supports a multi-site dashboard. You add a GSC_SITE_URLS setting with each property separated by commas, then ask for a dashboard across all sites.

Keep It Safe and Accurate

• Treat credential files like passwords. Never post them or commit them to GitHub.

• Check the package name. The guide I used reports that an older instruction pointed to gsc-mcp-server, which turned out to be a different maintainer’s package. Install exactly what the official README of your chosen server says, and read its source if you can.

• Know where your data goes. The server runs on your machine, but anything Claude reads becomes part of your conversation. Avoid connecting client sites without permission.

• Verify the big claims. The server returns exact numbers from Google, but Claude’s explanation of why traffic moved can be a guess. Treat causes as hypotheses and double-check key figures in Search Console.

Quick Troubleshooting

References

• Suganthan Mohanadasan, Google Search Console MCP: Step by Step Setup Guide

• Suganthan-Mohanadasan/Suganthans-GSC-MCP on GitHub

• Trevor Lasn, Google Search Console MCP for Claude Code (mcp-gsc)

• mcp-google-search-console on PyPI