list_sitesLABSCO SUMMARY
Search Console questions answered where you are already thinking.
The useful ones — which queries earn impressions and no clicks, which pages slipped this month, whether that new URL is even indexed — take four screens in the web interface and one exchange here.
What it is
A read-only window onto Google Search Console: search analytics by page, query, country, device and date, URL inspection, and sitemap status, across the properties the service account can reach.
What you get
- Clicks, impressions, CTR and average position over a date range you set
- Breakdowns by query, page, country, device, search appearance or date, up to the API's row limit per request
- Filters on query and page, switching to regex when you prefix the value
- Search types beyond web — image, video, news, discover and Google News
- Period-over-period comparison for week-on-week and month-on-month trends
- The list of properties the account has access to
- Index coverage for a URL — indexed, excluded or erroring, with crawl and mobile usability detail
- Sitemap status, including how many of each sitemap's URLs are indexed
Requirements
A Google service account, added as a user on every Search Console property you want to read. It cannot submit URLs or change any setting.
Setup effort
Build from source — git clone https://github.com/sarahpark/google-search-console-mcp.git
USE CASES
01
Finding pages that lost traffic this month
Compare the same window against the one before it, broken down by page.
02
Spotting queries you rank for but nobody clicks
Pull the high-impression, low-click rows and read them against the titles those pages carry.
03
Checking whether a new page is in the index
Inspect the URL and read its coverage and crawl state rather than guessing from a site: search.
04
Seeing which country or device a change came from
Break the same date range down by country and by device before drawing a conclusion.
05
Confirming a sitemap is being read
Check its status and how many of its URLs are indexed.
4 tools
Listed in project docs. Your client may show a different list.
search_analyticsinspect_urllist_sitemapsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Node.js with npm, to build it from source
- GOOGLE_APPLICATION_CREDENTIALS in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/sarahpark/google-search-console-mcp.git
cd google-search-console-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"gsc": {
"command": "node",
"args": [
"<YOUR_PATH_TO_GOOGLE_SEARCH_CONSOLE_MCP>/build/index.js"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"gsc": {
"type": "stdio",
"command": "node",
"args": [
"<YOUR_PATH_TO_GOOGLE_SEARCH_CONSOLE_MCP>/build/index.js"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"gsc": {
"type": "stdio",
"command": "node",
"args": [
"<YOUR_PATH_TO_GOOGLE_SEARCH_CONSOLE_MCP>/build/index.js"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}
