list_accountsLABSCO SUMMARY
Multi-account without a restart, and the destructive tools stay off.
Agencies end up running one server per client and reconnecting to switch. Here the account is resolved per call from a config file, so the workflow stays continuous — which matters more than it sounds when the task is comparing two clients' data in one sitting. The safety choice is the right one too: submitting or deleting a sitemap is a real change to how Google crawls a site, and it takes an explicit environment flag rather than a confirmation the model can talk itself past.
What it is
A Search Console MCP server built for operators who manage more than one property. Accounts are declared in a config file and resolved per call, so one running server addresses many Search Console accounts and switching between them does not mean restarting anything.
What you get
- Account routing as first-class behaviour: inspect the configured accounts, change the default, and refresh authentication in place —
list_accounts,set_default_account,reauthenticate - Property inventory: which properties an account can reach and what permissions it has on them —
list_properties,get_site_details - Search analytics five ways — a straight query, a performance overview, a period comparison, an advanced query and a per-page breakdown —
get_search_analytics,get_performance_overview,compare_periods,get_advanced_search_analytics,get_search_by_page - Indexing inspection, singly and in batch, plus an indexing-issues check —
inspect_url,batch_inspect_urls,check_indexing_issues - Sitemap management: list, read, submit and delete — with the two write operations held behind a destructive flag —
list_sitemaps,get_sitemap,submit_sitemap,delete_sitemap - Transient Search Console API failures retried with backoff rather than surfacing as errors you have to re-ask about
Requirements
Google Search Console access per account, authenticated either through the OAuth desktop flow or a service account. Configuration is file-driven: copy accounts.example.json to ~/.config/mcp-search-console/accounts.json and point GSC_ACCOUNTS_CONFIG at it. GSC_ALLOW_DESTRUCTIVE must be set to true before sitemap submit and delete will run at all. Install with python -m pip install mcp-search-console-multi or launch with uvx mcp-search-console-multi; the package is mcp-search-console-multi (version 0.1.3) over stdio, with MCP_TRANSPORT switchable to SSE for remote hosting. The README describes this as a beta package.
Setup effort
Follow the published steps — python -m pip install mcp-search-console-multi
USE CASES
01
Working across several clients in one session
List the configured accounts and switch the default between them, without restarting the server or reconnecting the client.
02
Explaining a traffic change
Compare the two periods directly and read the per-page breakdown, rather than exporting two reports and diffing them.
03
Finding out why a page is not showing up
Inspect the URL, then run the indexing-issues check when one page turns out not to be the only one.
04
Checking a batch of URLs after a migration
Run the batch inspection over the moved pages instead of pasting them into the web UI one at a time.
05
Managing sitemaps deliberately
Read the current sitemaps freely, and set the destructive flag only for the session where you actually intend to submit or delete one.
17 tools
Listed in project docs. Your client may show a different list.
set_default_accountreauthenticatelist_propertiesget_site_detailsget_search_analyticsget_performance_overviewcompare_periodsget_advanced_search_analyticsget_search_by_pageinspect_urlbatch_inspect_urlscheck_indexing_issueslist_sitemapsget_sitemapsubmit_sitemapdelete_sitemapBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- Python with pip (or uvx)
- Search Console access through a Google OAuth desktop client or a service account
- GSC_ACCOUNTS_CONFIG in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
python -m pip install mcp-search-console-multi
mkdir -p ~/.config/mcp-search-consoleCreate ~/.config/mcp-search-console/accounts.json in the shape of the repository's accounts.example.json: a "default" account name, and under "accounts" one entry per Search Console login — "type": "oauth" with the client_secrets_file of a Google OAuth desktop client and a token_file path, or "type": "service_account" with its credentials_file
Add the configuration to your client, with GSC_ACCOUNTS_CONFIG set to the full path of that file (/Users/<YOUR_USERNAME> is your own home directory)
On the first call for an OAuth account a browser window opens to sign in to Google; the token is then saved to that account's token_file
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"search-console": {
"command": "uvx",
"args": [
"mcp-search-console-multi"
],
"env": {
"GSC_ACCOUNTS_CONFIG": "/Users/<YOUR_USERNAME>/.config/mcp-search-console/accounts.json"
}
}
}
}
