How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Google Search Console logo. Google Search Console MCP server connector.

Google Search Console MCP Server

Google Search Console is a free service from Google that helps you monitor, maintain, and troubleshoot your site's presence in Google Search results, including search analytics, sitemaps, and URL indexing status.

ToolsTools
13
Last updatedLast Updated
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Google Search Console MCP Server?

The Google Search Console MCP server gives AI agents structured, permission-aware access to Google Search Console through the Model Context Protocol. With 13 pre-built actions, agents can read, create, and update Google Search Console data on behalf of authorized users.

Willow ships the Google Search Console MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Google Search Console is being used by every AI agent in your stack.

Tools

List Sites

List all sites (properties) in the authenticated user's Search Console account, along with the user's permission level for each. Use this to discover which property URLs are available before querying analytics, sitemaps, or URL inspection.

Get Site

Retrieve information about a specific Search Console property, including the authenticated user's permission level. Use the exact property identifier as shown in Search Console.

Add Site

Add a site (property) to the authenticated user's Search Console account. Note that adding a property does not verify ownership; verification must be completed separately in the Search Console UI.

Delete Site

Remove a site (property) from the authenticated user's Search Console account. This only removes the property from the user's account; it does not delete the website itself.

Query Search Analytics

Query search traffic data (clicks, impressions, CTR, and average position) for a property over a date range, grouped by one or more dimensions and optionally filtered. This is the full-power reporting tool; for common cases prefer Get Top Queries, Get Top Pages, or Get Performance Over Time.

Get Top Queries

Get the top-performing search queries for a property over a date range, ranked by clicks. Returns each query with its clicks, impressions, CTR, and average position. Convenient preset over search analytics grouped by 'query'.

Get Top Pages

Get the top-performing pages for a property over a date range, ranked by clicks. Returns each page URL with its clicks, impressions, CTR, and average position. Convenient preset over search analytics grouped by 'page'.

Get Performance Over Time

Get daily search performance for a property over a date range, grouped by date and sorted oldest to newest. Returns clicks, impressions, CTR, and average position per day. Use this for trend analysis and time-series charts.

List Sitemaps

List the sitemaps submitted for a property, or the sitemaps contained within a sitemap index file. Returns each sitemap's path, submission/download times, pending state, warnings, errors, and content counts.

Get Sitemap

Retrieve information about a specific sitemap submitted for a property, including its processing state, warnings, errors, and content type counts.

Submit Sitemap

Submit a sitemap for a property so Google can discover and crawl its URLs. The sitemap must already be hosted at the given URL under the property.

Delete Sitemap

Remove a previously submitted sitemap from a property. This tells Google to stop using the sitemap; it does not delete the sitemap file from your server.

Inspect URL

Inspect the index status of a URL in Google, equivalent to the URL Inspection tool in Search Console. Returns the indexing verdict, coverage state, robots.txt and indexing state, last crawl time, page fetch state, and Google's chosen canonical.

Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Google Search Console MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-google-search-console": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-search-console"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-google-search-console": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/google-search-console"
    }
  }
}

Claude Code

CLI
claude mcp add willow-google-search-console --transport http https://<org>.mcp-s.com/mcp/mcp/google-search-console

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/google-search-console",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Google Search Console

Willow adds the layer Google Search Console and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Google Search Console MCP Server FAQ

What is the Google Search Console MCP server?

The Google Search Console MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Google Search Console data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Google Search Console MCP server different from the official one?

The official Google Search Console MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Google Search Console MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Google Search Console MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Google Search Console, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Google Search Console actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Google Search Console MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Google Search Console MCP locally, you'll see it.

What does the Google Search Console MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Google Search Console MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.