Google Search Console MCP

Connect Google Search Console to Cursor, Claude, or Gemini. Ask questions in plain English and get real SEO data back.

What you can ask your AI once it's set up

Show me the biggest SEO opportunities for my site. Which pages are losing clicks? Find keywords ranking positions 4–15 that I can push to page 1. Split branded vs non-branded traffic for the last 90 days. Which pages have bad CTR for their ranking position? Inspect these URLs and tell me what's wrong with indexing. Generate a Markdown SEO report for the last 28 days.

- Google— give the MCP access to your Search Console data
- Your AI app— tell Cursor / Claude / Gemini how to run it

This is just a container for API access. It is not your website.
- Go toconsole.cloud.google.com
- Click the project dropdown at the top →New Project
- Name itGSC SEO MCPand clickCreate
- Make sure it's selected in the top dropdown after creation
- Go toAPIs & Services → Library
- SearchGoogle Search Console API→ click it → clickEnable
- Optional: also enableIndexing APIif you want theindexing_*tools (only useful for JobPosting/livestream pages)
- Go toIAM & Admin → Service Accounts
- ClickCreate service account
- Name:gsc-seo-mcp→ clickCreate and continue
- Skip the role assignment → clickContinue→ clickDone
- Copy the service account email — looks like:

gsc-seo-mcp@your-project-id.iam.gserviceaccount.com

Don't commit this file to GitHub. Treat it like a password.
- Opensearch.google.com/search-console
- Select your property
- Go toSettings → Users and permissions → Add user
- Paste the service account email, set permission toFull, clickAdd

{ "mcpServers": { "gsc-seo": { "command": "npx", "args": ["-y", "gsc-seo-mcp"], "env": { "GSC_AUTH_MODE": "service_account", "GSC_KEY_FILE": "/absolute/path/to/gsc-seo-mcp.json", "GSC_SITE_URL": "sc-domain:example.com" } } } }

Windows path tip — use forward slashes or double backslashes:

"GSC_KEY_FILE": "C:/Users/your-name/keys/gsc-seo-mcp.json"

Use this if you want to connect with your own Google account via browser login.
- Go toAPIs & Services → OAuth consent screen
- ChooseExternal(works for Gmail accounts) → fill in app name, email → save
- If the app is in testing mode, add your Gmail underTest users
- Go toAPIs & Services → Credentials → Create credentials → OAuth client ID
- Application type:Desktop app→ name itGSC SEO MCP Desktop→ clickCreate
- ClickDownload JSON— save it like:

- Mac/Linux:/Users/your-name/keys/gsc-oauth-client.json
- Windows:C:/Users/your-name/keys/gsc-oauth-client.json

{ "mcpServers": { "gsc-seo": { "command": "npx", "args": ["-y", "gsc-seo-mcp"], "env": { "GSC_AUTH_MODE": "oauth", "GSC_OAUTH_SECRETS_FILE": "/absolute/path/to/gsc-oauth-client.json", "GSC_TOKEN_FILE": "/absolute/path/to/gsc-oauth-token.json", "GSC_SITE_URL": "sc-domain:example.com" } } } }

GSC_TOKEN_FILEis where the MCP saves your login token after the first browser sign-in. If you leave it out, it saves to~/.gsc-seo-mcp/token.jsonby default.

If Google shows an "unverified app" warning, clickAdvanced → Continue— this is your own OAuth app, it's fine.

Node.js 20+ is required.Download hereif you don't have it.

{ "mcpServers": { "gsc-seo": { "command": "npx", "args": ["-y", "gsc-seo-mcp"], "env": { "GSC_AUTH_MODE": "service_account", "GSC_KEY_FILE": "/absolute/path/to/service-account.json", "GSC_SITE_URL": "sc-domain:example.com", "GSC_BRAND_TERMS": "mybrand,mybrand.com" } } } }

- Mac:~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:%APPDATA%\Claude\claude_desktop_config.json

{ "mcpServers": { "gsc-seo": { "command": "npx", "args": ["-y", "gsc-seo-mcp"], "env": { "GSC_AUTH_MODE": "service_account", "GSC_KEY_FILE": "/absolute/path/to/service-account.json", "GSC_SITE_URL": "sc-domain:example.com" } } } }

{ "mcpServers": { "gsc-seo": { "command": "npx", "args": ["-y", "gsc-seo-mcp"], "env": { "GSC_AUTH_MODE": "service_account", "GSC_KEY_FILE": "/absolute/path/to/service-account.json", "GSC_SITE_URL": "sc-domain:example.com" } } } }

claude mcp add --transport stdio \ --env GSC_AUTH_MODE=service_account \ --env GSC_KEY_FILE=/absolute/path/to/service-account.json \ --env GSC_SITE_URL=sc-domain:example.com \ gsc-seo -- npx -y gsc-seo-mcp

Edit~/.gemini/settings.json(or.gemini/settings.jsonin your project):

{ "mcpServers": { "gsc-seo": { "command": "npx", "args": ["-y", "gsc-seo-mcp"], "env": { "GSC_AUTH_MODE": "service_account", "GSC_KEY_FILE": "/absolute/path/to/service-account.json", "GSC_SITE_URL": "sc-domain:example.com" }, "timeout": 120000, "trust": false } } }

Use the exact format from Search Console:

sc-domain:example.com ← domain property (recommended) https://www.example.com/ ← URL-prefix property (include the trailing slash)

Tools don't show up in my AI appMake sure Node.js 20+ is installed. Check your MCP config usesnpx -y gsc-seo-mcpexactly. All file paths must be absolute (not~/or relative).

Service account shows no propertiesYou need to add the service account email to Search Console underSettings → Users and permissions.

URL Inspection failsThe URL must belong to the property inGSC_SITE_URL. For URL-prefix properties, use the exact prefix with protocol and trailing slash.

OAuth doesn't open the browserSetGSC_OAUTH_PORT=0to let it pick a free port. If you're on a remote machine, you'll need to run this locally instead.

- Search Analytics rows are sorted by clicks. The API has internal row limits, so not every possible row is included.
- GSC_DATA_STATE=allincludes fresh data. Usefinalfor finalized reporting numbers.
- URL Inspection shows Google's index state, not a live crawl.
- The Indexing API is for JobPosting and BroadcastEvent pages only — it's not a general indexing shortcut.

- Never commit service account keys, OAuth secrets, or token files to Git.
- Use read-only Search Console permissions if you don't need write tools.
- Reviewdelete_site,delete_sitemap,submit_sitemap, andindexing_publish_urlcalls before approving them.

- Create a Google Cloud project
- Enable APIs
- Create credentials
- Search Console users and permissions
- Search Analytics API
- URL Inspection API
- Indexing API
- Model Context Protocol

SEO + GEO MCP: live Google Search Console data, keyword and page analysis, site audit and SEO tasks — 21 tools.