Free Google Search Console MCP: No-Code Setup

  • No Google Cloud setup: one Google sign-in, no Python, nothing to host.
  • Every property in one chat: ask once and get an answer for each connected site.
  • Works in any MCP client: Claude, ChatGPT, Claude Code and Cursor, with GA4, Google Ads and 30+ more sources in the same answer.
  • Free forever plan: unlimited connected accounts, up to 30 days of history (15 days in AI chats).
Try free

What is a Google Search Console MCP server?

A Google Search Console MCP server lets an AI assistant like Claude or ChatGPT read your Search Console data through the Model Context Protocol (MCP). You ask in plain language, and the assistant calls Google’s Search Console API for clicks, impressions, CTR, positions, URL inspection and sitemaps.

  • Quick setup: paste https://mcp.portermetrics.com/mcp into Claude, ChatGPT or Cursor and sign in with Google. Full steps
  • Works in: Claude, ChatGPT, Claude Code, Cursor, VS Code and Codex
  • Data: 27 Search Console fields, up to 25,000 rows per request
  • Changes: sitemaps only, each after your approval
  • Price: free plan, paid plans from $15 per site a month
  • Official Google server: none for Search Console as of November 2026
Use cases

Google Search Console MCP use cases

Porter’s Google Search Console MCP connects your properties to Claude, ChatGPT and any MCP client through one hosted server URL. Ask in plain language and the answer comes from Google’s Search Console API, live. Porter covers four kinds of SEO work: reports, research, audits and management.

Reports

  • Live dashboards: a Porter-hosted dashboard that syncs on its own. Start from the Google Search Console dashboard templates.
  • Search Console with GA4 and Google Ads: clicks next to organic sessions, key events and paid search terms, blended into one table.
  • Weekly SEO report: clicks, impressions, CTR and position against last week, with three takeaways.
  • Every client property: one prompt compares all connected sites, worst first.

Research

  • Striking distance: queries at positions 5 to 15 with enough impressions to matter, and the page that ranks for each.
  • Content decay: pages losing clicks month over month, and the queries they lost.
  • Branded vs non-branded: how much traffic came from people who typed your name.
  • Competitor SEO research: keywords, search results and competitor pages beyond your own property, paid with automation credits.

Audits

  • Indexing: index status, Google-selected canonical and last crawl for every URL you list.
  • Cannibalization: two of your pages trading places on one query, and which one should own it.
  • Low-CTR titles: pages that hold their position while CTR drops, with new titles drafted.
  • Traffic drops and core updates: clicks and positions before and after a Google core update or a site release, by page and query, so you see what was hit.
  • Pages that rank but don’t engage: high clicks with low GA4 engagement, flagged for a rewrite.

Management

  • Sitemaps: list, submit or resubmit sitemaps. Claude or ChatGPT shows the change and sends it only after you approve.
  • Scheduled reports: your weekly report by email, on the day you choose.

Example answer

Demo data, from a fictional property. Prompt: “List queries from the last 90 days ending 3 days ago with Average Position between 5 and 15 and at least 5,000 Impressions, with the page that ranks for each.”

QueryPageImpressionsAverage PositionClicksCTR
running shoes for flat feet/guides/flat-feet-shoes/18,4007.24122.2%
trail running shoes women/trail/womens/9,6508.91411.5%
best marathon shoes 2026/guides/marathon-shoes/22,10011.41980.9%
waterproof running shoes/collections/waterproof/6,1206.11903.1%

Claude then drafts a new title and meta description for each page, starting with the one closest to page one.

Reference

Google Search Console MCP server reference

Porter’s Search Console MCP reads Google’s Search Console API for every property your Google account can open. The same server URL works in each AI client below, and the same connection feeds Porter’s other destinations.

Search Console fields

27 fields: 5 metrics and 22 dimensions.

Metrics: Clicks · Impressions · CTR · Average Position

Dimensions: Query · Page URL · Country · Device · Search Appearance · Search Type (Web, Image, Video, News, Discover, Google News) · Date · Week · Month · Quarter · Year

Read actions: list properties (site_list) · query search performance (searchanalytics_query) · inspect a URL (urlinspection_inspect) · list sitemaps (sitemap_list)

Write actions (each asks you first): submit a sitemap (sitemap_submit) · remove a sitemap (sitemap_delete)

Not available: indexing requests, user management and site verification stay in Search Console.

Filters: equals, contains, not contains and regex (include or exclude) on Query, Page URL, Country, Device and Search Appearance

Rows and freshness: up to 25,000 rows per request, past the 1,000-row table in Search Console. Google’s data runs about 2 to 3 days behind: ask for final data only, or include the latest partial days.

See all 27 Google Search Console fields

Other destinations

The same Search Console connection also sends data to Data Studio (formerly Looker Studio), BigQuery and Google Sheets, at no extra cost.

Security and trust

Safety and security

Porter’s Search Console MCP reads your properties without changing them. Reports, research and URL inspection are reads. Sitemap submissions and removals are the only changes, and nothing is sent until you approve it in the chat.

Reads by default

Queries, pages, clicks and URL inspection never change your property. Changes happen only when you ask for one and approve it.

Google sign-in, official API

You sign in with Google in Porter. Porter works through Google’s Search Console API, with the scopes Google defines in its Search Console API authorization guide.

Your Search Console permissions apply

Porter sees only the properties your Google account can open, with the rights Google gives that account, as Search Console users and permissions explains.

Sitemap removal is permanent

Removing a sitemap can’t be undone, so the chat flags it before asking. To bring it back, submit the same URL again.

Revoke access anytime

Disconnect the property in Porter whenever you want. Access lives in your Google connection, not in a key file on someone’s machine.

Setup

How to set up the Google Search Console MCP server

Paste this server URL into your AI app, then sign in with Google:

https://mcp.portermetrics.com/mcp

First, create a free Porter account and connect Google Search Console: Create → pick your AI app as the destination → Google Search Console → sign in with Google → select your properties.

Before you connect: sign in to Search Console with the same Google account and check that it opens each property’s Performance report. A Domain property (sc-domain:example.com) and a URL-prefix property (https://www.example.com/) are separate, so pick the one your team reports on. If a property is missing, ask its owner to add you, per Google’s property permissions guide.

How to install Google Search Console MCP in Claude

  1. Open claude.ai and go to Settings → Connectors.
  2. Click Add custom connector.
  3. Name it Porter and paste https://mcp.portermetrics.com/mcp.
  4. Click Add, then sign in with the Google account you use in Porter and approve access.
  5. Ask Claude your first Search Console question.

On Team and Enterprise plans, an owner adds the connector first. Anthropic’s custom connector guide covers the same steps.

Watch the Claude setup demo

How to install Google Search Console MCP in ChatGPT

ChatGPT has two routes to the same data. The Porter Metrics app in ChatGPT’s app directory works on any plan with apps. The Porter MCP gets every new tool the day Porter ships it, on Business, Enterprise and Edu workspaces.

Porter Metrics app: in ChatGPT, open Apps, search “Porter Metrics”, click Connect and sign in with the Google account you use in Porter.

Porter MCP:

  1. Open ChatGPT on the web and go to Plugins.
  2. Click +, then Add custom MCP server.
  3. Name it Porter and paste https://mcp.portermetrics.com/mcp under Connection.
  4. Choose OAuth, tick “I understand and want to continue” and click Create as a plugin.
  5. Sign in with the Google account you use in Porter.

Pro accounts can add it with read access only, per OpenAI’s custom MCP server guide.

Watch the ChatGPT setup demo

How to install Google Search Console MCP in Claude Code, Cursor, VS Code and Codex

Pick your coding agent. Each one uses the same server URL and a Google sign-in, so no API key or credentials file sits in a config.

  1. Add Porter’s plugin in Claude Code. It installs the Porter connector and Porter’s skill in one step.
    /plugin marketplace add portermetrics/porter /plugin install porter-metrics@portermetrics
  2. Ask for your data. The first time, your browser opens: sign in with the Google account you use in Porter.
  3. No plugins? Add the server directly instead:
    claude mcp add --transport http porter https://mcp.portermetrics.com/mcp
  4. Check: /mcp shows porter as connected. Ask: “Which Google Search Console accounts can you see?”
  1. Open Cursor Settings → Tools & Integrations and click New MCP Server. Cursor opens mcp.json.
  2. Paste this and save.
    { "mcpServers": { "porter": { "url": "https://mcp.portermetrics.com/mcp" } } }
  3. Click Connect next to porter and sign in with the Google account you use in Porter.
  4. Check: porter shows a green dot in Tools & Integrations. Open an Agent chat. Ask: “Which Google Search Console accounts can you see?”
  1. Open the Command Palette (Ctrl/Cmd+Shift+P) and run MCP: Add Server → HTTP.
  2. Paste https://mcp.portermetrics.com/mcp, name it porter and choose Global. Or add it to .vscode/mcp.json:
    { "servers": { "porter": { "type": "http", "url": "https://mcp.portermetrics.com/mcp" } } }
  3. Allow the sign-in prompt and sign in with the Google account you use in Porter.
  4. Check: open Copilot Chat in Agent mode; Porter’s tools appear under the tools icon. Ask: “Which Google Search Console accounts can you see?”
  1. Add Porter from your terminal.
    codex mcp add porter --url https://mcp.portermetrics.com/mcp
  2. Sign in. Your browser opens: sign in with the Google account you use in Porter.
    codex mcp login porter
  3. Check: codex mcp list shows porter as logged in. Start codex. Ask: “Which Google Search Console accounts can you see?”

The same URL works in Windsurf, Cline, Zed and any client that supports remote MCP servers over HTTP.

Add Porter’s skill

Porter’s skill teaches Claude which Porter tools to call for each SEO task, so answers need fewer retries. In claude.ai, download https://mcp.portermetrics.com/skill.zip and upload it in Settings → Capabilities → Skills. In Claude Code, Porter’s plugin adds it for you, and other agents can run npx skills add portermetrics/porter.

Test the connection

Paste this into a new chat. It only reads data.

Use Porter only. List my Google Search Console properties and my access level on each. For the first property, show clicks, impressions, CTR and average position for the 7 days ending 3 days ago, grouped by page, top 5 rows. Say so if a property returns no data.

Guides and videos

Prompts

Google Search Console MCP prompts

Copy a prompt into Claude or ChatGPT, then swap in your brand terms, thresholds and dates. End date ranges 3 days ago, when Google marks the data final.

Reporting prompts

Connection test

List my Search Console properties, then show Clicks, Impressions, CTR and Average Position by Week for the last 4 full weeks, ending 3 days ago.

Weekly SEO report

Build my weekly Search Console report for last full week vs the week before: Clicks, Impressions, CTR and Average Position, top 10 Query and Page URL, Clicks by Device. End with 3 takeaways.

Live dashboard

Build a live Porter dashboard for my property with Clicks, Impressions, CTR and Average Position by Week, top queries and top pages for the last 3 months.

Client property comparison

Compare every connected property by Clicks, Impressions, CTR and Average Position for the last 28 days ending 3 days ago, with the change vs the 28 days before. Worst first.

Research and audit prompts

Striking distance

For the last 90 days ending 3 days ago, list Query and Page URL pairs with Average Position between 5 and 15 and at least 500 Impressions. Sort by Impressions and suggest one change for the top 10.

Content decay

Compare Clicks by Page URL for the last 3 full months vs the 3 months before. Rank the 15 pages that lost the most Clicks and show the queries each one lost.

Cannibalization

For the last 90 days, find queries where 2 or more pages each have at least 100 Impressions. Show Clicks and Average Position per page and recommend which page should own the query.

Indexing check

Inspect these 10 URLs and show index status, Google-selected canonical and last crawl date. Flag any URL that isn’t indexed.

Rankings vs GA4

List my top 20 pages by Clicks last month. Next to each, show GA4 Sessions, Engagement rate and Key events from google / organic.

Management prompts

Sitemap resubmit

List my submitted sitemaps with their status. If the main sitemap shows errors, show me its URL and resubmit it only after I confirm.

Scheduled report

Every Monday, email me last week’s Search Console summary: Clicks, Impressions, CTR, Average Position and the biggest mover.
Who this is for

Who this is for

Porter’s Search Console MCP fits SEO teams who check rankings every week and want the answer without exporting a table.

SEO agencies and freelancers

  • Every client property in one chat: one prompt answers for all of them.
  • Client reports: a live dashboard link instead of a monthly export.

In-house SEO specialists

  • Striking distance: the next round of edits starts with queries that already rank.
  • Search next to revenue: rankings beside GA4 key events, so priorities follow conversions.

Content marketers

  • Refresh list: pages ranked by lost clicks, with the queries each one lost.
  • Title tests: new titles drafted where CTR fell at the same position.
Comparison

Open-source Search Console MCPs vs. Porter

Google has no official Search Console MCP as of November 2026, so the choice is a hosted server like Porter’s or an open-source server you run, like mcp-gsc on GitHub. Both read Google’s Search Console API. Here is where they differ.

PorterOpen-source (mcp-gsc)
SetupGoogle sign-in, then one URL in your AI appPython 3.11+, a Google Cloud project with the Search Console API, an OAuth client or service account
Steps before your first question3: connect Search Console in Porter, paste the URL, sign in with Google5 in Google Cloud (project, Search Console API, credentials, consent screen, key download), then a local install and config
Credential files on your computerNoneAn OAuth client secrets or service-account JSON, plus a saved token
HostingHosted at mcp.portermetrics.com/mcpRuns on your own machine
Several properties in one promptYes, every connected property at onceOne configuration per setup
Other sources in the same chatGA4, Google Ads and 30+ moreSearch Console only
Competitor SEO researchKeywords, search results and competitor pages, with automation creditsNo
Live dashboards and scheduled reportsYesNo
Data Studio, BigQuery, Google SheetsSame connectionNo
PriceIncluded in every Porter plan, free plan tooFree, MIT license

The mcp-gsc column follows its GitHub README (as of November 2026). Pick mcp-gsc to run the code yourself for one property. Pick Porter for every property, every channel and no setup.

Porter vs other hosted Search Console MCPs

Connector platforms such as OOMOL and Composio also host a Search Console MCP. They’re built for developers wiring many apps into agents. Porter is built for SEO and marketing reporting:

1

Every property at once

One prompt answers for all your connected sites and clients, not one property per setup.

2

Search Console next to 30+ sources

GA4, Google Tag Manager, Google Ads, Meta Ads and Shopify, blended in one answer.

3

Competitor SEO data

Keywords, live search results and competitor pages, next to your own Search Console numbers.

4

Reports outside the chat

Live dashboards, scheduled email reports, and the same data in Data Studio, BigQuery and Google Sheets.

5

Sign in, no keys

One URL and a Google sign-in. No API key, team header or service-account file in a config.

6

Claude and ChatGPT both covered

A remote MCP URL, plus an approved app in ChatGPT’s app directory.

Google Search Console MCP pricing

The Google Search Console MCP is included in every Porter plan, the free-forever plan too. Reporting is billed per connected account, and each Search Console site counts as one account.

  • 14-day trial: everything unlimited, no credit card.
  • Free forever: unlimited connected accounts, 30 days of history (15 days in AI chats), 100 automation credits a month.
  • Paid Reporting: from $15 per account a month, or $12.50 billed annually.
  • Unlimited questions: AI chats, queries and dashboards are included; you pay only for connected accounts.
5 accounts
Monthly billing
$40
Annual billing, per month
$33.33
Per account
$8.00

Reporting price for connected accounts, in USD. AI chats, queries and dashboards are unlimited. Annual billing is 10 months for 12.

The more accounts you connect, the lower the price per account. See the full calculator on Porter pricing.

Frequently asked questions

Does Google have an official Search Console MCP?

No. As of November 2026, Search Console isn't on Google's list of products with MCP servers, and Google's open-source MCP covers Analytics, not Search Console. You connect Search Console to an AI app through a hosted server like Porter's, an open-source server like mcp-gsc, or your own API code.

Is there a Google Search Console MCP on GitHub?

Yes, several open-source ones. The most used is mcp-gsc, a Python server with 20 tools. Each needs your own Google Cloud project and credentials. Porter's is hosted, so there's nothing to install.

What is the Google Search Console MCP server URL?

Porter's Google Search Console MCP server URL is https://mcp.portermetrics.com/mcp. Paste it into Claude, ChatGPT or another MCP client, then sign in with Google and pick your properties.

Is GSC MCP the same as Google Search Console MCP?

Yes. GSC is the short name for Google Search Console, so a GSC MCP is a Search Console MCP server.

Can it see past the 1,000-row limit in Search Console?

Yes. Search Console's own tables stop at 1,000 rows (Google's 1,000-row table limit), while Google's API returns up to 25,000 rows per request.

How much Search Console history can it read?

Google keeps 16 months of Search Console data. Porter's paid plans read whatever the API returns; the free plan keeps up to 30 days (15 days in AI chats), and the 14-day trial has no history limit.

Troubleshooting

Why don't the numbers match Search Console?

Search Console days follow Pacific time, and the newest days stay empty until Google marks them final. With Page URL in the question, Google counts each URL shown, so page totals run higher than site totals.

Why does Google say I don't have permission for the site?

Your Google account needs access to that exact property in Search Console. If Porter shows it as unverified, ask the property owner to add you as a user, or connect the Google account that already has access. A Domain property and its URL-prefix version need separate access.

Why does the query work but return no rows?

Check the property, the date range, the search type (Web, Image, News) and any filters. An empty result isn't a permission error, and days newer than about 3 days ago may not be final yet.

Start free

Connect Search Console to Claude, ChatGPT or any MCP client and run your first SEO report today.

Start free: unlimited connected accounts, no credit card.