Orkas Orkas
Home Blog Google Search Console MCP
Product

Google Search Console MCP: Three Ways to Set It Up, and a First Audit

Google doesn't make a Search Console MCP server, so you choose a community server, a hosted one or an app with a connector built in. Here's what each takes, what the API leaves out, and a first audit you can check yourself.

A Google Search Console MCP server gives an AI agent such as Claude, Claude Code, Codex or Cursor access to the Search Console API. The agent can pull your clicks, impressions, click-through rate and average position, check whether a page is indexed, and list your sitemaps. You ask in plain language, for example "which pages rank on page one but get no clicks?", and the agent runs the queries and works through the rows. This guide compares the three ways to set one up, explains what the API leaves out, and walks through a first audit you can check against Search Console yourself.

The short answer: as of November 9, 2026, Google has no official Search Console MCP server. Google publishes one for Google Analytics, and neither Claude's nor ChatGPT's directory has a Search Console connector from Google, Anthropic or OpenAI. Your options are a free community server that you run yourself, which needs a Google Cloud project; a hosted server that you sign in to with Google; or an app with a built-in connector, such as Orkas, where you click Connect. All three read the same API, and it doesn't list every query: Google leaves out anonymized queries, which made up 46.77% of traffic in an Ahrefs study of 887,534 Search Console properties.

What a Search Console MCP can and can't do

Every Search Console MCP server, community or commercial, calls the same free Search Console API. What it can do depends on that API, listed below from Google's API reference and usage limits.

What you ask forAPILimits
Clicks, impressions, CTR and position by query, page, country, device, date or search appearanceSearch Analytics16 months of history, about 2–3 days behind; up to 25,000 rows per request and 50,000 rows a day per search type
Whether a URL is indexed, its last crawl, and the canonical Google choseURL InspectionOne URL per call; 2,000 calls a day per property
Your sitemaps and their errorsSitemapsReading needs read-only access; submitting or deleting needs full access
The properties you can seeSitesAdding or removing a property needs full access

Some things in Search Console have no API, so no MCP server can get them:

  • AI Overviews and AI Mode data. Google rolled out the generative AI performance report to all sites on August 31, 2026, but the API reference lists no search type or appearance for it.
  • Newer report options. The multimodal search type and the branded-queries filter are also missing from the API reference.
  • Testing a live page. URL Inspection reports the version in Google's index. The API docs say "you cannot test the indexability of a live URL."
  • The "Request indexing" button. It exists only in Search Console. Google's separate Indexing API, which some servers call, is officially only for job posting and livestream pages.

Three ways to connect Search Console to Claude, Claude Code or Codex

RouteSetupWhere your data goesCost
Community server you run, such as mcp-gscGoogle Cloud project, API, credentials and a config entryFrom your computer to GoogleFree
Hosted server, such as mcpsearchconsole.comSign in with Google, paste a server URL into your AI appThrough the provider's serversFree tier, then a subscription
Built-in connector in OrkasClick Connect, sign in with GoogleFrom your computer to GoogleFree connector
  • Community servers are free and the most capable. The most popular, AminForou/mcp-gsc, had 2,151 GitHub stars on November 9, 2026. Its source has 21 tools, including period comparisons, batch inspection of up to 10 URLs and, if you allow it, sitemap submission. The cost is setup: you create your own Google credentials. One r/TechSEO commenter called Google Cloud "the only friction".
  • Hosted servers are the quickest way into claude.ai or ChatGPT on the web. They are remote servers, so you add them by URL. Claude's help center says custom connectors work on every plan, but "Free users are limited to one custom connector." mcpsearchconsole.com lists a free plan with 40 data pulls a month on three properties, then €4.99 a month before VAT. Your Search Console data passes through the provider, so read its privacy terms first.
  • A built-in connector skips the Google Cloud setup. In Orkas you sign in with Google and the connector runs on your computer. It's read-only and has four tools, fewer than the community servers.

Run a community server yourself

These steps follow the mcp-gsc README as of version 0.4.2 (November 6, 2026). We didn't create a Google Cloud project for this guide, so check the README before you start.

  1. Create Google credentials. In the Google Cloud console, create a project, enable the Search Console API, and create an OAuth client ID of type Desktop app. Download its JSON file. For automation, create a service account instead, then add its email address in Search Console under Settings, Users and permissions, with Full access.
  2. Install uv. The README's recommended route runs the server with uvx, which handles Python for you. Without it, you need Python 3.11 or later.
  3. Add the server to your agent. In Claude Code:
    claude mcp add --env GSC_OAUTH_CLIENT_SECRETS_FILE=/path/to/client_secrets.json --transport stdio gsc -- uvx mcp-search-console
    In Codex:
    codex mcp add gsc --env GSC_OAUTH_CLIENT_SECRETS_FILE=/path/to/client_secrets.json -- uvx mcp-search-console
    We checked both commands with Claude Code 2.1.311 and Codex CLI 0.163.0. For Claude Desktop or Cursor, the README gives JSON config with the full path to uvx, because apps opened from the Dock or Start menu may not find it otherwise.
  4. Sign in once. On first use, a browser window opens for Google sign-in. Since 0.4.2, the server asks only for read-only access unless you set GSC_ALLOW_DESTRUCTIVE=true.

One catch the community guides don't mention: if your OAuth consent screen is set to External and left in Testing, Google's OAuth documentation says the refresh token expires after 7 days. You'd sign in again every week. To avoid that, publish the app to production or use a service account. A published app may show an "unverified app" warning, which Google lets personal-use apps with fewer than 100 users click through.

Connect Search Console in Orkas

Orkas is a desktop app for macOS and Windows where several AI agents work in one chat. Its Google Search Console connector is built in, so you don't need a Google Cloud project.

  1. Install Orkas and sign in. Download it for macOS or Windows. New accounts get 500 free credits for Orkas's built-in models, so you don't need an API key to start.
  2. Open Connectors. Click Connectors in the sidebar and find Google Search Console. The Data filter or the search box gets you there.
  3. Click Connect and sign in with Google. Click Connect, use the Google account that can see your property, and allow read-only access. The card moves to Connected.
  4. Ask for what you need. In a chat, type @ and choose the Google Search Console connector, or just describe the task. The agent lists your properties first, then queries the one you name.
  • It's read-only. Orkas asks Google only for the webmasters.readonly scope. The four tools list your properties, query performance data, list sitemaps and inspect a URL. Because they only read, Orkas runs them without asking you to approve each call. They can't submit sitemaps or request indexing, and one query returns at most 25,000 rows.
  • Queries go straight to Google. The connector runs on your computer and calls the Search Console API directly. Only the Google sign-in and token refresh go through Orkas's server, which holds the app's Google credentials.
  • SeoGeoAgent and your coding agents can use it. SeoGeoAgent, Orkas's built-in SEO agent, uses your real clicks, impressions and positions in its audits once Search Console is connected. If you've installed Claude Code, Codex, OpenCode, Hermes or OpenClaw and connected it in Orkas, it reaches the connector through Orkas's tool bridge, with no MCP setup of its own.
  • Need to write? Use Add MCP server on the Connectors page to add a community server as a local command. Orkas also has a Bing Webmaster Tools connector.

A first audit you can check

A good first request asks for numbers you can compare with Search Console in a minute, and makes the agent say what the data doesn't cover. Replace the property and the two URLs with your own:

Use the Google Search Console connector for sc-domain:example.com. For the last 28 days of complete data: 1) total clicks and impressions by date, and what share of them the query rows cover; 2) pages ranking between positions 5 and 15 with at least 100 impressions and a click-through rate under 2%, sorted by impressions; 3) the index status of https://example.com/new-page/ and https://example.com/old-page/. Put the date range on every table, and don't estimate anything the data doesn't show.

We ran this request with Claude Code in Orkas on November 9, 2026, and all four connector tools worked. We don't publish our own site's Search Console numbers, so the results below are a synthetic example: made-up figures for a fictional shop at example.com, showing what a careful answer looks like and how to check each part.

  • Totals by date (synthetic): 3,480 clicks and 151,200 impressions. These are the numbers to trust for the whole site. To check yours, open the Performance report, choose the same custom dates and search type, and compare the totals. They should come out close. A big gap usually means the agent added up query or page rows instead.
  • Query rows (synthetic): 642 rows covering 1,670 clicks, 48% of the total. The rest comes from queries Google anonymizes, which have no row in the report or the API. A share like this is normal: Ahrefs found that anonymized queries made up 46.77% of traffic in April 2025, and more on many sites. An agent that adds up query rows and calls it your traffic can be off by half.
  • Low-CTR pages (synthetic): 9 pages in positions 5 to 15 with at least 100 impressions and a CTR under 2%. The largest, /blog/linen-care/, had 2,140 impressions at an average position of 6.8 and 21 clicks, a 1.0% CTR. Those are the first titles and descriptions to look at. If your site serves languages at addresses ending in ?lang=, each version gets its own page row, so ask for them grouped.
  • URL inspection (synthetic): the old page is indexed, the new one isn't yet. https://example.com/old-page/, published in September, was "Submitted and indexed", last crawled October 3. https://example.com/new-page/, published two days before the check, was "Discovered - currently not indexed". To check, paste the same URL into the inspection box at the top of Search Console.

Five things that trip people up

  • Treating query rows as total traffic. Google's performance data guide says anonymized queries have no row, "if you sum up clicks for all the rows, you'll not find the same number of clicks as the chart totals." For totals, ask for data by date with no query filter.
  • Comparing page totals with site totals. Grouped by page, each URL that shows in a result is counted separately. Grouped by property, a result counts once for the whole site. So page rows can add up to more impressions than the site total.
  • Forgetting the delay. Data is "typically available after 2-3 days". The API returns finalized data unless asked for fresh data, so "the last 7 days" ends a few days before today.
  • Using the wrong property name. A domain property is written sc-domain:example.com. A URL-prefix property is the full address with its trailing slash, such as https://example.com/. Let the agent list your properties first and copy the name it returns.
  • Asking for too much at once. Each request returns at most 25,000 rows, and a query-and-page breakdown over 16 months fills that quickly. Ask for summaries, a filter or a shorter date range, and let the agent work through the rows rather than paste them all into the chat.

Which route should you pick?

Your situationPick
You use claude.ai or ChatGPT in the browserA hosted server, added by URL
You want every tool, including sitemap submission, and don't mind Google CloudA community server such as mcp-gsc
You want Claude Code, Codex and an SEO agent to read Search Console without Google CloudOrkas's built-in connector
Your site is too big for 25,000 rows per requestSearch Console's bulk data export to BigQuery, outside MCP

Questions

Does Google have an official Search Console MCP server?

No, not as of November 9, 2026. Search Console isn't on Google's list of official MCP servers or in Google Cloud's MCP list. Google publishes an MCP server for Google Analytics, which doesn't include Search Console data.

Is a Search Console MCP free?

The Search Console API is free, and so are community servers such as mcp-gsc and Orkas's connector. Hosted servers usually have a free tier with a monthly limit and a paid plan. The AI agent you connect still has its own cost, such as a Claude plan or Orkas credits.

Can an MCP server submit sitemaps or request indexing?

It can submit or delete sitemaps if it has full Search Console access, which some community servers offer. The Search Console API has no Request indexing function, so no server can do that for ordinary pages. Orkas's connector is read-only and does neither.

Why don't the MCP numbers match Search Console?

Usually because the agent added up query rows, which leave out anonymized queries, or mixed totals by page with totals by property. Ask for totals by date with no query filter, and the same dates and search type as the report. The totals should then come out close.

Does it work with Claude Code and Codex?

Yes. Add a community server with claude mcp add or codex mcp add, or add a hosted server by URL. In Orkas, Claude Code and Codex use the built-in Search Console connector through Orkas's tool bridge, with no setup in either tool.

What Is Agentic SEO? covers the bigger picture: an agent runs the SEO work on live data, and a person approves what ships.

Claude SEO skill →

Search Console in your agent's chat Connect Search Console once and let Claude Code, Codex or SeoGeoAgent read it. Orkas is free on macOS and Windows. New accounts get 500 credits for the built-in Orkas model.
Download Orkas — free