Google Search Console (mcp-gsc)
MCP server by Amin Foroutan
Analyze Google Search Console performance, URL inspection, indexing and sitemaps through natural language.
Install Google Search Console (mcp-gsc)
Runs on your machine. Your client starts it with this command:
Needs uv (Python) on your computer. The setup steps below show where the command goes in each client.
GSC_OAUTH_CLIENT_SECRETS_FILEPath to your Google OAuth client secrets JSON (or use a service account with GSC_CREDENTIALS_PATH and GSC_SKIP_OAUTH=true).
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/search-consoleAbout
Connects Google Search Console to an AI assistant so you can query search performance data, inspect URLs, check indexing status and manage sitemaps. The README also lists comparisons between periods, advanced search analytics with sorting, and batch URL inspection. It is a community project, not made by Google.
It runs locally over stdio with uvx (uvx mcp-search-console) and needs Python 3.11 or newer. Authenticate with Google OAuth by pointing GSC_OAUTH_CLIENT_SECRETS_FILE at a client secrets file, or use a service account with GSC_CREDENTIALS_PATH and GSC_SKIP_OAUTH=true. Add and delete tools stay disabled unless GSC_ALLOW_DESTRUCTIVE is set to true.
What you can do
- List the Search Console properties you can access
- Query search performance and advanced search analytics
- Compare search performance between two periods
- Inspect URLs and batch-check indexing status
- Surface rich-result issues from URL inspection
- Work with sitemaps for a property
- Check auth status with get_capabilities
Tools
Google Search Console (mcp-gsc) lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.
Example prompts
List all my GSC properties
Compare search performance for example.com over the last 28 days with the previous period
Inspect indexing for my top 10 pages on example.com
Find queries at positions 11 to 20 with high impressions
Set up
Every client starts Google Search Console (mcp-gsc) on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio search-console --env "GSC_OAUTH_CLIENT_SECRETS_FILE=<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>" -- uvx mcp-search-console- Start Claude Code and type
/mcp. 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
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"search-console": {
"command": "uvx",
"args": [
"mcp-search-console"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"search-console": {
"command": "uvx",
"args": [
"mcp-search-console"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>"
}
}
}
}Needs uv (Python) 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:
{
"servers": {
"search-console": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-search-console"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "${input:gsc-oauth-client-secrets-file}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "gsc-oauth-client-secrets-file",
"description": "GSC_OAUTH_CLIENT_SECRETS_FILE",
"password": true
}
]
}Needs uv (Python) on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"search-console": {
"command": "uvx",
"args": [
"mcp-search-console"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>"
}
}
}
}- 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 search-console --env "GSC_OAUTH_CLIENT_SECRETS_FILE=<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>" -- uvx mcp-search-consoleOr edit ~/.codex/config.toml directly:
[mcp_servers.search-console]
command = "uvx"
args = ["mcp-search-console"]
env = { GSC_OAUTH_CLIENT_SECRETS_FILE = "<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>" }Needs uv (Python) on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "GSC_OAUTH_CLIENT_SECRETS_FILE=<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>" search-console uvx mcp-search-consoleThis 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": {
"search-console": {
"command": "uvx",
"args": [
"mcp-search-console"
],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<YOUR_GSC_OAUTH_CLIENT_SECRETS_FILE>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs uv (Python) on your computer. Replace the placeholders with your own values.
Embed
Show Google Search Console (mcp-gsc) 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
[](https://mcp.tc/i/search-console)<a href="https://mcp.tc/i/search-console"><img src="https://mcp.tc/i/search-console/badge.svg" alt="Google Search Console (mcp-gsc) 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
<script src="https://mcp.tc/w/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
<iframe src="https://mcp.tc/embed/search-console" title="Google Search Console (mcp-gsc) 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/search-console.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google Search Console (mcp-gsc) card to your site.
Add the mcp.tc card for Google Search Console (mcp-gsc), 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/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="search-console"><a href="https://mcp.tc/i/search-console">Google Search Console (mcp-gsc) 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
[](https://mcp.tc/i/search-console)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its PyPI package: each new version shows up here, with edits by its owner.
FAQ
Can I paste mcp.tc/i/search-console into my MCP client?
No. Google Search Console (mcp-gsc) 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 uvx mcp-search-console.
Does Google Search Console (mcp-gsc) need an API key?
Yes. It reads GSC_OAUTH_CLIENT_SECRETS_FILE from its environment, and GSC_OAUTH_CLIENT_SECRETS_FILE is a secret. Put the value in your client’s config on your own machine, never in a shared file.
Is Google Search Console (mcp-gsc) a remote or a local server?
Local. Your client starts it as a process on your computer with uvx mcp-search-console, which needs uv (Python).
What can Google Search Console (mcp-gsc) do?
You can list the Search Console properties you can access, query search performance and advanced search analytics and compare search performance between two periods.
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 Google Search Console (mcp-gsc)?
Partly. It runs on your computer, so we follow its PyPI 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 Google Search Console (mcp-gsc)’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 Amin Foroutan. This page was built from Google Search Console (mcp-gsc)’s public metadata, last checked on 3 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.