Connect Claude to your Google Search Console data. Query search analytics, check indexing status, and manage sitemaps through natural conversation.
- Node.js 18+ installed
- Google Search Console account with at least one verified property
- Claude Desktop app installed
npx gsc-mcp-server --setupThis will open a browser for you to sign in with your Google account. That's it!
Open your Claude Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server configuration:
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "gsc-mcp-server"]
}
}
}If you already have other MCP servers, add it with a comma:
{
"mcpServers": {
"other-server": { ... },
"google-search-console": {
"command": "npx",
"args": ["-y", "gsc-mcp-server"]
}
}
}Quit and reopen Claude Desktop to load the new server.
Once configured, ask Claude things like:
| What you want | Example prompt |
|---|---|
| Top search queries | "What are my top 10 search queries this month?" |
| Page performance | "How is my /blog page performing in search?" |
| Check indexing | "Is https://mysite.com/new-post indexed?" |
| Compare periods | "Compare my search traffic this week vs last week" |
| Find opportunities | "Show me queries with high impressions but low CTR" |
| Manage sitemaps | "List my sitemaps" or "Submit my new sitemap" |
| Tool | Description |
|---|---|
gsc_list_sites |
List all your Search Console properties |
gsc_search_analytics |
Query clicks, impressions, CTR, and position |
gsc_inspect_url |
Check if a URL is indexed |
gsc_list_sitemaps |
List submitted sitemaps |
gsc_get_sitemap |
Get sitemap details |
gsc_submit_sitemap |
Submit a new sitemap |
gsc_delete_sitemap |
Remove a sitemap |
"Permission denied" for a site? → Make sure your Google account has access to that property in Search Console
Need to re-authenticate?
→ Run npx gsc-mcp-server --setup again
Session expired?
→ Run npx gsc-mcp-server --setup to sign in again
The server works out of the box with shared OAuth credentials. For production use or higher rate limits, you can use your own:
- Go to Google Cloud Console
- Create a project and enable the Search Console API
- Create OAuth 2.0 credentials (Desktop app)
- Save credentials to
~/.gsc-mcp-server/credentials.json - Run
npx gsc-mcp-server --setupto authenticate
All data stays on your machine. See our Privacy Policy.
MIT
I'm Sofian Bettayeb.
By day, I'm a martech consultant, working with billion-dollar brands. By night, I build tools like AI SEO Copilot (15k+ installs), AEO Copilot, and blueprints like Webflow SEO Checklist (1k+ downloads) to help my Webflow friends make money with SEO and AEO.
In between, I ride my bikes and play with my kids in Bern, Switzerland.