We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

SEO Tools: Google Search Console

MCP server by antohins

Query Google Search Console search analytics, inspect URLs and list sitemaps with read-only access.

Runs locally (Runs on your machine: its page has the install command)Runs with npxNeeds an API key

Install SEO Tools: Google Search Console

Runs on your machine. Your client starts it with this command:

npx -y seo-tools-mcp-gsc

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

  • GOOGLE_CLIENT_ID optional Google OAuth client ID (Desktop app).
  • GOOGLE_CLIENT_SECRET secret optional Google OAuth client secret.
  • GSC_REFRESH_TOKEN secret optional Google OAuth refresh token (or obtain via gsc_oauth_start).
  • GSC_SITE_URL optional Default GSC property, e.g. sc-domain:example.com.
  • GSC_SA_JSON optional Path to a service-account JSON key (alternative auth path).
  • GSC_OAUTH_PORT optional Localhost port for the OAuth loopback receiver (default 8585).

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/seo-tools-google-search-console

About

Connects an assistant to Google Search Console. It can run Search Analytics queries, inspect URLs, list and read site properties, and list and read sitemaps. All tools are read-only and return strict JSON. It is the gsc server from the seo-tools-mcp project, which also ships separate servers for other SEO services.

Runs locally over stdio through the npm package seo-tools-mcp-gsc with npx. Authentication is Google OAuth (desktop client with a refresh token, or an interactive flow started from a tool) or a service account JSON key. Default site property and OAuth port can be set through environment variables.

What you can do

  • Run Search Analytics queries on a Search Console property
  • Inspect the index status of a URL
  • List Search Console sites and get site details
  • List sitemaps and read sitemap details
  • Authenticate with OAuth or a service account
  • Set a default property through configuration

Tools

SEO Tools: Google Search Console lists its tools only to clients with a key, so we can’t show them here.

Example prompts

  • Show my top 20 queries by clicks for the last 28 days on sc-domain:example.com

  • Inspect https://example.com/pricing and tell me if it is indexed

  • List all sitemaps submitted for my site and their status

  • Which Search Console properties do I have access to?

Set up

Every client starts SEO Tools: Google Search Console on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio seo-tools-google-search-console --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GSC_REFRESH_TOKEN=<YOUR_GSC_REFRESH_TOKEN>" -- npx -y seo-tools-mcp-gsc
  1. Start Claude Code and type /mcp. seo-tools-google-search-console should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "seo-tools-google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "GSC_REFRESH_TOKEN": "<YOUR_GSC_REFRESH_TOKEN>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "seo-tools-google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "GSC_REFRESH_TOKEN": "<YOUR_GSC_REFRESH_TOKEN>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "seo-tools-google-search-console": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_SECRET": "${input:google-client-secret}",
        "GSC_REFRESH_TOKEN": "${input:gsc-refresh-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "google-client-secret",
      "description": "GOOGLE_CLIENT_SECRET",
      "password": true
    },
    {
      "type": "promptString",
      "id": "gsc-refresh-token",
      "description": "GSC_REFRESH_TOKEN",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "seo-tools-google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "GSC_REFRESH_TOKEN": "<YOUR_GSC_REFRESH_TOKEN>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add seo-tools-google-search-console --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GSC_REFRESH_TOKEN=<YOUR_GSC_REFRESH_TOKEN>" -- npx -y seo-tools-mcp-gsc

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.seo-tools-google-search-console]
command = "npx"
args = ["-y", "seo-tools-mcp-gsc"]
env = { GOOGLE_CLIENT_SECRET = "<YOUR_GOOGLE_CLIENT_SECRET>", GSC_REFRESH_TOKEN = "<YOUR_GSC_REFRESH_TOKEN>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" -e "GSC_REFRESH_TOKEN=<YOUR_GSC_REFRESH_TOKEN>" seo-tools-google-search-console npx -- -y seo-tools-mcp-gsc

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "seo-tools-google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "GSC_REFRESH_TOKEN": "<YOUR_GSC_REFRESH_TOKEN>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

Embed

Show SEO Tools: Google Search Console in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![SEO Tools: Google Search Console on mcp.tc](https://mcp.tc/i/seo-tools-google-search-console/badge.svg)](https://mcp.tc/i/seo-tools-google-search-console)
HTML
<a href="https://mcp.tc/i/seo-tools-google-search-console"><img src="https://mcp.tc/i/seo-tools-google-search-console/badge.svg" alt="SEO Tools: Google Search Console on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/seo-tools-google-search-console.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/seo-tools-google-search-console" title="SEO Tools: Google Search Console on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/seo-tools-google-search-console.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the SEO Tools: Google Search Console card to your site.

Markdown
Add the mcp.tc card for SEO Tools: Google Search Console, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/seo-tools-google-search-console.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="seo-tools-google-search-console"><a href="https://mcp.tc/i/seo-tools-google-search-console">SEO Tools: Google Search Console on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![SEO Tools: Google Search Console on mcp.tc](https://mcp.tc/i/seo-tools-google-search-console/badge.svg)](https://mcp.tc/i/seo-tools-google-search-console)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow SEO Tools: Google Search Console and we’ll email you when something changes.

  1. , Automatic check

    Tracking started: version 1.8.0.

FAQ

Can I paste mcp.tc/i/seo-tools-google-search-console into my MCP client?

No. SEO Tools: Google Search Console runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y seo-tools-mcp-gsc.

Does SEO Tools: Google Search Console need an API key?

Yes. It reads GOOGLE_CLIENT_SECRET and GSC_REFRESH_TOKEN from its environment, and GOOGLE_CLIENT_SECRET and GSC_REFRESH_TOKEN are secrets. Put the values in your client’s config on your own machine, never in a shared file.

Is SEO Tools: Google Search Console a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y seo-tools-mcp-gsc, which needs Node.js.

What can SEO Tools: Google Search Console do?

You can run Search Analytics queries on a Search Console property, inspect the index status of a URL and list Search Console sites and get site details.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to SEO Tools: Google Search Console?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read SEO Tools: Google Search Console’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with antohins. This page was built from SEO Tools: Google Search Console’s public metadata, last checked on 5 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.