Google Search Console MCP Server

What is Google Search Console MCP Server?

Google Search Console MCP Server is an MCP server that exposes the Google Search Console API for use in n8n workflows via the MCP Client node. It is intended for n8n users who want to automate Search Console data retrieval and analysis.

How to use Google Search Console MCP Server?

Install Python 3.7+, clone the repository, create a virtual environment, install dependencies, and run the setup script to configure a Google service account credentials file. In n8n, add an MCP Client (STDIO) node, set the command to the Python path, arguments to the server script, and the environment variable SERVICE_ACCOUNT_JSON pointing to your credentials file. Then call any of the available tools by selecting "Execute Tool" in the MCP Client node.

Key features of Google Search Console MCP Server

• List all Search Console sites
• Retrieve search analytics data
• View top search queries and pages
• Check URL indexing status
• Fetch sitemap information
• Query search terms for a specific URL
• All tools available via n8n MCP Client node

Use cases of Google Search Console MCP Server

• Automate weekly top‑query reports in n8n
• Monitor URL indexing status for multiple sites
• Extract sitemap data to audit website structure
• Build a dashboard that refreshes Search Console metrics
• Integrate search analytics with other n8n workflows

FAQ from Google Search Console MCP Server

What does the server require to run?

Python 3.7+ and a Google service account with access to the desired Search Console properties.

How do I set up authentication?

Run the included setup script (setup-credentials.sh) and either provide an existing service account JSON file or create a new one in Google Cloud Console. Then grant the service account email access in Google Search Console settings.

What tools does the server provide?

It provides eight tools: list_sites, get_search_analytics, get_top_queries, get_top_pages, get_queries_for_url, inspect_url, and list_sitemaps.

Where are credentials stored?

Credentials are stored locally in a JSON file. The .gitignore file prevents it from being pushed to Git.

What transport does the server use?

The server uses STDIO transport, as it is designed for n8n’s MCP Client (STDIO) node.