SEO Skill

Google Search Console MCP

Add one URL to your AI client, sign in with Google, and ask about your clicks, impressions, CTR, positions, queries and index status. There is no Google Cloud project to create and nothing to install.

Run it in a terminal, then sign in with Google.

Or run it on your machine

Installs the CLI, signs you in and adds the skill to your agents. Site crawls and Bing data run this way, on your own machine. A crawl fetches many pages, and Bing blocks our hosted server.

A Search Console MCP server you add with one URL

The SEO Skill server lives at https://seoskill.dev/mcp. Your AI client connects to it, you sign in with the Google account that can see your Search Console, and the agent can read that data on each request. The sign-in asks for read-only access, so nothing your agent does changes your Search Console settings.

Google does not publish a Search Console MCP server. Its list of Google MCP servers had none for Search Console when we checked on 11 November 2026, so every Search Console MCP is built on the public Search Console API. SEO Skill reads that same API with your own sign-in, so the numbers match what you see in Search Console.

Connect Search Console to 5 AI clients

You need a Google account that can see at least one Search Console property. That is the whole list. Each client below takes a minute, and the Search Console integration page has the steps for VS Code, Gemini CLI, Windsurf and Le Chat too.

Connect Google Search Console to Claude Code

  1. 1

    Run this in a terminal. The user scope makes it available in every project:

    claude mcp add --transport http --scope user seoskill https://seoskill.dev/mcp
  2. 2

    Start Claude Code, type /mcp, choose seoskill and sign in. Or run claude mcp login seoskill from the shell.

A browser tab opens for Google sign-in. Claude Code keeps the token, so you sign in once.

Connect Google Search Console to Codex

  1. 1

    Add the server, then sign in. The CLI, IDE extension and desktop app share this config:

    codex mcp add seoskill --url https://seoskill.dev/mcp
    codex mcp login seoskill
  2. 2

    Check it with /mcp in Codex, or codex mcp list.

codex mcp login opens the Google sign-in in your browser. Codex keeps the token for later sessions.

Connect Google Search Console to ChatGPT

  1. 1

    Open Plugins, choose +, then Add custom MCP server.

  2. 2

    Name it seoskill and enter the server URL under Connection:

    https://seoskill.dev/mcp
  3. 3

    Choose OAuth for authentication, confirm, and choose Create as a plugin. Sign in with Google when ChatGPT asks.

  4. 4

    In a chat, type @ and pick seoskill.

Custom MCP servers depend on your ChatGPT plan. OpenAI lists Business, Enterprise and Edu workspaces, where an admin may need to create the plugin, and Pro accounts for read-only servers like this one.

Connect Google Search Console to Claude.ai and Claude Desktop

  1. 1

    Open Customize, then Connectors. Choose Add, then Add custom connector.

  2. 2

    Name it seoskill, enter the server URL and choose Continue:

    https://seoskill.dev/mcp
  3. 3

    If Claude asks how to register the OAuth client, choose Register automatically. Then choose Add and sign in with Google.

  4. 4

    In a chat, turn it on from the + menu under Connectors.

Every Claude plan can add custom connectors, and the free plan allows one. On Team and Enterprise plans an owner adds the connector under Organization settings first, then each member connects their own Google account.

Connect Google Search Console to Cursor

  1. 1

    Add the server to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

    {
      "mcpServers": {
        "seoskill": { "url": "https://seoskill.dev/mcp" }
      }
    }
  2. 2

    Open the MCP section of Cursor's settings and sign in when seoskill asks for it.

On Enterprise teams an admin can limit which MCP servers are allowed.

Run it on your machine instead

Prefer to keep the Google token on your own computer? The open source CLI reads the same data and adds a local MCP server to Claude Code, Codex and Cursor during setup:

npm i -g seo && seo start

The local route also gives your agent the site crawl and Bing Webmaster Tools, which the hosted server leaves to the CLI.

6 prompts to run once Search Console is connected

Type these in plain words. Your agent picks the tool, and every result names the tool to run next. Each prompt also has a terminal command if you want to see the same result without an agent.

See which sites your agent can read

Which Search Console properties can you read?

The agent lists the Search Console and Google Analytics properties your linked Google accounts can see. Domain properties look like sc-domain:example.com. If a site is missing, add the Google account that owns it on your account page.

Get the overview for last month

What happened in search for example.com in the last 28 days?

In a terminal

seo report --site example.com

Clicks, impressions, CTR and position against the previous period, split by device, with the pages and queries that moved most. Every section of the report shows its row count and top rows, so the agent knows where to look next.

Find quick wins and page two queries

Show me the striking-distance queries and quick wins for example.com

Striking distance lists queries just outside the top positions for pages that already rank. Quick wins are queries at positions 4 to 10 with a click-through rate below your own site's curve for that position, which usually means the title or description needs a rewrite.

Check why one page lost its clicks

Why did https://example.com/pricing lose clicks this month?

In a terminal

seo page --url https://example.com/pricing

The agent loads the page live (status, redirect, title, canonical, robots), asks Google's URL Inspection whether it is indexed, and lists the page's queries against the previous period. A noindex tag and a lost ranking look the same in a clicks chart. They look nothing alike here.

Compare before and after a release or a Google update

Compare example.com before and after 2026-09-15, just the /blog/ pages

In a terminal

seo compare --site example.com --date 2026-09-15 --pages /blog/

Equal periods either side of the date, with the pages and queries that moved and any Google ranking updates in the window. An update that lines up with a drop is reported as timing only, because overlap alone cannot show what caused it.

Find pages that dropped out of Google

Which pages on example.com lost their clicks, and are they still indexed?

In a terminal

seo index --site example.com

Pages that kept 20% or less of their clicks over the last 28 days, each checked live, with Google's own index status for the top ones. It also gives Google's indexing reason for up to 100 known URLs a run.

A worked example: one query split across 7 pages

We ran this on seoskill.dev while rebuilding this page. The prompt was:

Which of my pages show up for searches containing "search console mcp", with impressions and position?

The agent called the raw rows tool with a query filter, by query and page, for 13 August to 7 November 2026. For "google search console mcp" alone, Search Console showed 7 different seoskill.dev URLs:

PageImpressions (average position)
/features/search-console523 (64.2)
/integrations/google-search-console/cursor57 (82.1)
/alternatives/search-console-mcp51 (80.9)
/integrations/google-search-console36 (81.0)
/integrations/google-search-console/vs-code27 (85.8)
/alternatives and /features/google-analytics19 and 4

This page got 523 of the 717 impressions (73%) and the best position, so it is the one we built out. A page split like that is what the report's cannibalization section looks for: queries where more than one of your pages gets impressions, with each page's share. None of these rows had a click yet, so the table shows where Google is testing the site. It says nothing about traffic so far.

What each tool reads from Search Console

Ask aboutWhat comes back
The whole siteThe SEO report overview: totals against the previous period by device, with top pages and queries, and Google Analytics sessions for the same dates when a property matches. The Google Analytics MCP server page covers the rest of that data.
OpportunitiesReport sections for quick wins, low CTR, striking distance, second page, content decay and cannibalization.
DropsThe traffic drop section finds the day a lasting change started. seo index finds pages that lost their clicks.
Google updatesOne ranking update laid over your clicks and impressions, with the folders, pages and queries that moved most.
AI-style searchesQueries shaped like chat prompts and follow-ups, grouped into one question each. A heuristic: Search Console does not mark AI Mode.
One URLseo page: live page facts, URL Inspection status and the page's queries.
Anything elseRaw rows by query, page, date, country, device or search appearance, each with the previous period.

Hosted, local or self-hosted from GitHub

The open source Search Console MCP servers on GitHub, such as mcp-gsc and mcp-server-gsc, run on your machine. Most ask you to create a Google Cloud project, turn on the Search Console API and download an OAuth client or a service account key first. Pick one of those if you want to read and change every line of the server code, or need sitemap and indexing write tools.

Pick the hosted SEO Skill server if you want Search Console in claude.ai, ChatGPT or Claude on your phone, where a local server cannot run, or if you would rather skip the Google Cloud step. The CLI is the middle option: open source on GitHub and npm, local, and signed in with Google during seo start. The comparison of Search Console MCP servers shows how each one signs in and what it costs, checked on their own pages.

Free on demand, $50 a month for the weekly audit

Every tool your agent calls on demand is free, with no usage cap. The server fetches what the agent asks for, returns it and keeps none of it. It stores only your linked Google accounts and any keys you save, encrypted.

The one paid part is the weekly site audit, at $50 a month per site. It runs on our servers without you asking: a weekly crawl, up to 2,000 URL Inspection checks a day, and an alert when a page drops out of Google's index. For those sites it keeps what the audit needs, such as index check results and the last two crawls. Your agent can start it with "Add example.com to the weekly site audit", which returns a Stripe Checkout link for you to open.

2 things Search Console data cannot tell you

Search Console hides some rare queries for privacy, so query rows never add up to the site total. The reports say when a section is empty or capped, rather than turning a missing row into zero.

The last two or three days are not final. The reports stop at the latest final day (on Google's Pacific time calendar), so a comparison never reads a half-counted day as a drop.

Questions about the Search Console MCP

Is there an official Google Search Console MCP server?

No. As of November 2026 Google publishes MCP servers for many Cloud and Workspace products, but not for Search Console. Every Search Console MCP, SEO Skill included, reads the public Search Console API.

Is the Google Search Console MCP free?

Yes for everything your agent asks on demand: reports, page checks, URL Inspection, comparisons and raw rows, with no cap. Only the weekly site audit costs money, $50 a month per site.

Do I need a Google Cloud project or an API key?

No. You add the server URL to your client and sign in with Google. Keyword and backlink research is the one part that uses a key, your own DataForSEO or Ahrefs key, and it is optional.

Can my agent change anything in Search Console?

The Google sign-in asks for read-only access. Your agent can read performance data and inspect URLs, and it cannot submit sitemaps, request indexing or change a property.

Can I connect more than one Google account?

Yes. Add a client's or a work Google account on your account page. Each request uses the linked account that can read the site you asked about.