How do I connect Google Search Console MCP Server to Claude?

Run `claude mcp add surendranb-google-search-console-mcp -- uvx google-search-console-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Google Search Console MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Google Search Console MCP Server do?

Google Search Console MCP Server documents 8 tools to the agent, including delete_sitemap, get_search_analytics, inspect_url. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Google Search Console MCP

Unclaimed

by surendranb

Google Search Console MCP Server for Claude, Cursor, Windsurf and other MCP Clients

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'surendranb-google-search-console-mcp' -- 'uvx' 'google-search-console-mcp'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

ai-agentsclaudecursorgoogle-search-consolemcpmcp-servermodel-context-protocolsearch-analyticsseo

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

8 of 8 tools

Documented tools (8)

From project documentation. A server handshake does not verify each tool’s description or behavior.

delete_sitemap

siteurl (string), feedpath (string)

get_search_analytics

siteurl (string), startdate (string), enddate (string), dimensions (list), rowlimit (int)

inspect_url

siteurl (string), inspectionurl (string)

list_sitemaps

siteurl (string)

list_sites

(none)

skill_read

skillname (string)

skills_list

(none)

submit_sitemap

siteurl (string), feedpath (string)

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Google Search Console MCP Server

How do I connect Google Search Console MCP Server to Claude?: Run `claude mcp add surendranb-google-search-console-mcp -- uvx google-search-console-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Google Search Console MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Google Search Console MCP Server do?: Google Search Console MCP Server documents 8 tools to the agent, including delete_sitemap, get_search_analytics, inspect_url. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.