Connects to Google Search Console to retrieve search performance, URL inspection, and sitemap data, and to analyze keyword opportunities, CTR issues, cannibalization, traffic changes, content gaps, and indexing/sitemap health. Sitemap submission and deletion are available only when write mode is enabled.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
An MCP server that connects Claude, Cursor and other AI assistants to Google Search Console.
It gives the assistant the raw data (search performance, URL inspection, sitemaps) and does the analysis on top: which keywords are one push from page one, which pages rank but are not clicked, which pages compete with each other, what lost traffic and why, and how much of your sitemap is indexed.
It runs on your machine, talks only to Google's API, and is read-only unless you switch writing on.
"How did organic search do in the last 28 days compared with the month before?"
"Which keywords are we close to ranking on page one for?"
"Which pages rank in the top 10 but hardly get clicked? Suggest better titles."
"Traffic dropped last week. What happened?"
"Are any of our pages competing for the same keyword?"
"Is https://example.com/pricing indexed? If not, why not?"
"How much of our sitemap is indexed, and what is wrong with the rest?"
"Pick the five blog posts most worth refreshing and write a brief for each."
What to use it for goes through each of these: what runs, what comes back and what to do with it.
Related MCP server: GSC-MCP
It analyses, not only fetches. The opportunity tools return a ranked list of things to act on, with the numbers behind each.
Estimates come from your own site. Expected click-through is measured on your data, not taken from a generic table.
It says what the numbers do not show. Row caps, samples, hidden queries, incomplete days and empty comparison periods are stated in every result.
Forgiving inputs. Say example.com or paste a page URL. Leave out the dates and you get the last 28 complete days.
Read-only by default, with errors that tell you how to fix them and a doctor command that checks the setup.
You need Node.js 22 or newer and a Google account with access to the Search Console properties you want to use.
Both ways are free. The authentication guide has every click.
Service account | Your own Google account (OAuth) | |
Best for | Agencies, servers, automation | One person with many properties |
Sees | Only properties you add it to | Everything your account can see |
Setup | Create a key, add its email as a user on each property | Create a "Desktop app" client, sign in once in the browser |
Service account: in Google Cloud enable the Google Search Console API, create a service account, download a JSON key, then in Search Console add the service account's email under Settings > Users and permissions for each property.
Your own account: in Google Cloud enable the Google Search Console API, create an OAuth client of type Desktop app, download its JSON, then run:
GSC_OAUTH_CLIENT_FILE=/path/to/client_secret.json npx -y @pixfrix/search-console-mcp auth loginclaude mcp add search-console \
--env GSC_SERVICE_ACCOUNT_KEY=/path/to/service-account.json \
-- npx -y @pixfrix/search-console-mcpIf you signed in with auth login, leave out the --env line.
Open Settings > Developer > Edit Config and add:
{
"mcpServers": {
"search-console": {
"command": "npx",
"args": ["-y", "@pixfrix/search-console-mcp"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY": "/path/to/service-account.json"
}
}
}
}Restart Claude Desktop afterwards.
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"search-console": {
"command": "npx",
"args": ["-y", "@pixfrix/search-console-mcp"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY": "/path/to/service-account.json"
}
}
}
}Add to .vscode/mcp.json:
{
"servers": {
"search-console": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@pixfrix/search-console-mcp"],
"env": {
"GSC_SERVICE_ACCOUNT_KEY": "/path/to/service-account.json"
}
}
}
}The server speaks MCP over stdio. Run npx -y @pixfrix/search-console-mcp as the command and pass the environment variables from Configuration.
On Windows, use forward slashes or doubled backslashes in JSON paths (C:/keys/gsc.json). If your client cannot start npx directly, use "command": "cmd" with "args": ["/c", "npx", "-y", "@pixfrix/search-console-mcp"].
GSC_SERVICE_ACCOUNT_KEY=/path/to/service-account.json npx -y @pixfrix/search-console-mcp doctor[ ok ] Credentials: service account (seo-bot@my-project.iam.gserviceaccount.com)
[ ok ] Google sign-in
[ ok ] Search Console API
[ ok ] Properties (2):
sc-domain:example.com [siteFullUser]
https://shop.example.com/ [siteRestrictedUser]If a step fails, doctor says what to change. Then ask your assistant: "List my Search Console properties."
Guide | What is in it |
Each job with the question to ask, what comes back and what to do next | |
Where the numbers come from, the rules behind each analysis, limits and safety | |
Service account and browser sign-in, step by step | |
Every tool and parameter |
Tool | What it answers |
| Which properties can this account read? |
| How is the site doing? Totals against a comparison period, the trend, and the top queries, pages, countries, devices and search appearances, in one call |
| Any custom question: every dimension (including hourly data), regex filters, every search type, paging to any depth, sorting by any metric |
| What changed? Gainers, decliners, new and lost rows against the previous period, the previous year or a custom range |
| Did traffic drop or spike, and was it one day or a lasting shift? |
| How much of the traffic is people searching for the brand, and how is the rest doing? |
Tool | What it answers |
| Which keywords rank just below the top results and would pay off fastest? |
| Which results rank well but get clicked far less than their position should earn? |
| Which queries are split between several of my pages? |
| Which pages or queries lost the most clicks, and was it rankings, impressions or click-through? |
| Where does the site show up without a page that serves the search, and which questions are people asking? |
| Everything about one URL: its queries, which to target, devices, countries, trend and index status |
Tool | What it answers |
| Is this URL indexed, and if not, why? |
| The same for up to 50 URLs, as one table |
| How much of my sitemap is indexed, and what is wrong with the rest? |
| Which sitemaps are submitted, when were they last read, and do they have errors? |
| Submit or resubmit a sitemap. Only with |
| Remove a sitemap from Search Console. Only with |
Clients that support MCP prompts (Claude Desktop and Claude Code show them as slash commands) get six ready-made workflows:
Prompt | What it produces |
| What moved in the last seven days and why |
| A prioritised action plan across every opportunity tool |
| When a drop started, where it is concentrated and the likely cause |
| The existing pages most worth updating, with what to change |
| Sitemap and indexing problems, by importance |
| A data-backed brief for one URL |
Everything is set through environment variables. Only credentials are required.
Variable | Purpose |
| Path to a service account JSON key |
| The key itself as a JSON string, for hosts without a file system |
| Google's standard variable, honoured when the two above are not set |
| Path to an OAuth "Desktop app" client secret file, used by |
| Default property, so you do not have to name it. Example: |
| Comma-separated brand names, to keep brand searches out of opportunity lists and to split branded from non-branded traffic |
|
|
| Where the saved sign-in lives. Default: |
Credentials are looked up in this order: GSC_SERVICE_ACCOUNT_JSON, GSC_SERVICE_ACCOUNT_KEY, GOOGLE_APPLICATION_CREDENTIALS, a saved auth login, then Google's Application Default Credentials.
search-console-mcp Start the MCP server (what your client runs)
search-console-mcp doctor Check credentials and list the properties you can read
search-console-mcp auth login Sign in with your own Google account (--write for sitemap changes)
search-console-mcp auth logout Forget the saved sign-inRun doctor first: it tests credentials, sign-in, API access and property permissions in order and explains the first failure.
Symptom | Cause and fix |
"The signed-in account cannot read this property" | The account is not a user of the property. In Search Console open Settings > Users and permissions and add it. For a service account, add its |
"Enable the Google Search Console API" | The API is off in your Google Cloud project. Enable it under APIs & Services > Library |
Sign-in expires every week | Your OAuth consent screen is in Testing. Publish it under Google Auth Platform > Audience |
"No Search Console property matches" | Call |
No data for a page | Search Console matches page URLs exactly, including |
Rows by query do not add up to the total | Expected. Google hides rare queries for privacy |
Numbers differ from the Search Console website | Compare the same dates. The website's default range runs up to today and includes incomplete days; the server's default stops at the last complete day |
The server does not appear in the client | Check the client's MCP log. On Windows try the |
The server runs locally as a child process of your MCP client. It contacts googleapis.com, and your own site when audit_sitemap_indexing reads a sitemap. There is no telemetry.
Credentials stay on your machine. A browser sign-in is stored as a refresh token in GSC_CONFIG_DIR. Delete it with auth logout.
The default scope is read-only. Search data returned by the tools becomes part of your conversation with the AI assistant, under that assistant's own privacy terms.
See SECURITY.md to report a vulnerability.
git clone https://github.com/PixFrixSystems/search-console-mcp.git
cd search-console-mcp
npm install
npm run build
npm testThe tests run against a stand-in for Google's API, so they need no credentials. With credentials, npm run live-check -- --site example.com runs every read-only tool against a real property and checks that the numbers agree with each other.
Contributions are welcome. See CONTRIBUTING.md.
Built and maintained by PixFrix. This project is not affiliated with or endorsed by Google. Google Search Console is a trademark of Google LLC.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
SEO audits, Search Console, GA4, keyword and backlink data for Claude, ChatGPT and Cursor.
SEO data your AI can cite: Search Console, GA4, keywords, backlinks, SERPs and AI visibility.
AI SEO agent on your Google Search Console data: audits, quick wins, content, WordPress publishing.
Turn Search Console data into SEO actions, content, publishing, indexing, and AI insights.
