Is Google Search Console MCP Server safe to use?

Google Search Console MCP Server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under AGPL-3.0.

How do I install Google Search Console MCP Server?

Google Search Console MCP Server supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can Google Search Console MCP Server do?

Google Search Console MCP Server provides 10 tools: list_sites, get_site, add_site, delete_site, query_search_analytics and 5 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with Google Search Console MCP Server?

Google Search Console MCP Server is compatible with claude-desktop, cursor, claude-code. It uses http transport.

Is Google Search Console MCP Server actively maintained?

Google Search Console MCP Server is recently maintained — last commit was 40 days ago.

Google Search Console MCP Server

mcp-google-search-console-crunchtools

Secure MCP server for Google Search Console analytics, sitemaps, and URL inspection

10 tools GitHub PyPI

No known CVEs

AGPL-3.0 license

Maintained

Last commit 40d ago

Works with most clients

Transport: http

10 tools · ~805 tok

Grade B · 0.4% of 200K ctx

MCPpedia last refreshed this data 13h ago

Edit this pageView history

Google Search Console MCP Server is an MCP server that secure MCP server for Google Search Console analytics, sitemaps, and URL inspection. Its tool list has not been published yet over http, requires no API key, and scores 78/100 on MCPpedia's security, maintenance and efficiency rubric.

Analytics Search

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktophttp · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-crunchtools-google-search-console": {
      "args": [
        "mcp-google-search-console-crunchtools"
      ],
      "command": "uvx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-crunchtools-google-search-console)](https://mcppedia.org/s/io-github-crunchtools-google-search-console)

Read me

What Google Search Console MCP Server does

Secure MCP server for Google Search Console. Query search analytics (clicks, impressions, CTR, position), manage sitemaps, inspect URL indexing status, and manage site properties.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

uvx 'mcp-google-search-console-crunchtools' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

78/100across 5 weighted dimensions

How we score →

0255075100

−22

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked mcp-google-search-console-crunchtools against OSV.dev.

Inventory

Tools (10)

Click any tool to inspect its schema.

~805 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Google Search Console MCP Server safe to use?: Google Search Console MCP Server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under AGPL-3.0.
How do I install Google Search Console MCP Server?: Google Search Console MCP Server supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can Google Search Console MCP Server do?: Google Search Console MCP Server provides 10 tools: list_sites, get_site, add_site, delete_site, query_search_analytics and 5 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Google Search Console MCP Server?: Google Search Console MCP Server is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Is Google Search Console MCP Server actively maintained?: Google Search Console MCP Server is recently maintained — last commit was 40 days ago.

Similar servers

Others in analytics / search

View all →

Context797

Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

61.1k 2

Gpt Researcher97

An autonomous agent that conducts deep research on any data using any LLM providers

29.1k 5

Tavily Mcp96

Production ready MCP server with real-time search, extract, map & crawl.

2.4k 4

Modelcontextprotocol96

The official MCP server implementation for the Perplexity API Platform

2.5k 4

MCP Security Weekly

Get CVE alerts and security updates for Google Search Console MCP Server and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Analytics Search

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktophttp · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-crunchtools-google-search-console": {
      "args": [
        "mcp-google-search-console-crunchtools"
      ],
      "command": "uvx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-crunchtools-google-search-console)](https://mcppedia.org/s/io-github-crunchtools-google-search-console)

Read me

What Google Search Console MCP Server does

Secure MCP server for Google Search Console. Query search analytics (clicks, impressions, CTR, position), manage sitemaps, inspect URL indexing status, and manage site properties.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

uvx 'mcp-google-search-console-crunchtools' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

mcp-google-search-console-crunchtools

Secure MCP server for Google Search Console. Query search analytics (clicks, impressions, CTR, position), manage sitemaps, inspect URL indexing status, and manage site properties.

Installation

uvx (recommended, zero-install)

claude mcp add mcp-google-search-console-crunchtools \
    --env GSC_CLIENT_ID=your_client_id \
    --env GSC_CLIENT_SECRET=your_client_secret \
    --env GSC_REFRESH_TOKEN=your_refresh_token \
    -- uvx mcp-google-search-console-crunchtools

pip

pip install mcp-google-search-console-crunchtools

Container (Podman/Docker)

podman run -d -p 8017:8017 \
    --env-file ~/.config/mcp-env/mcp-google-search-console.env \
    quay.io/crunchtools/mcp-google-search-console \
    --transport streamable-http --host 0.0.0.0

OAuth Setup

This server supports two authentication methods: browser-based OAuth (recommended) and environment variable (fallback).

Option A: Browser-Based OAuth (Recommended)

Browser-based OAuth handles token exchange automatically. When credentials expire, visit the /auth URL and click through Google's consent screen — no manual code exchange needed.

Step 1: Create a Google Cloud OAuth App

Go to Google Cloud Console
Create a new project (or select an existing one)
Navigate to APIs & Services > Library
Search for Google Search Console API and click Enable
Navigate to APIs & Services > Credentials
Click + CREATE CREDENTIALS > OAuth client ID
If prompted, configure the OAuth consent screen first:
- User type: External (or Internal if using Google Workspace)
- App name: anything (e.g., "MCP Search Console")
- Scopes: add https://www.googleapis.com/auth/webmasters
- Test users: add your Google account email
Back on Create OAuth client ID:
- Application type: Web application
- Name: anything (e.g., "MCP Search Console")
- Authorized redirect URIs: add your server's callback URL (e.g., https://mcp-gsc.example.com/oauth2callback)
Click Create — copy the Client ID and Client Secret

Step 2: Configure and Start

Create an env file:

cat > ~/.config/mcp-env/mcp-google-search-console.env << 'EOF'
GSC_CLIENT_ID=your_client_id
GSC_CLIENT_SECRET=your_client_secret
GSC_CREDENTIALS_DIR=/data
GSC_OAUTH_REDIRECT_URI=https://mcp-gsc.example.com/oauth2callback
EOF
chmod 600 ~/.config/mcp-env/mcp-google-search-console.env

Start the server with a persistent volume for credentials:

podman run -d -p 8017:8017 \
    --env-file ~/.config/mcp-env/mcp-google-search-console.env \
    -v mcp-gsc-data:/data:Z \
    quay.io/crunchtools/mcp-google-search-console \
    --transport streamable-http --host 0.0.0.0

Step 3: Authenticate

Visit https://mcp-gsc.example.com/auth in your browser. You'll be redirected to Google's consent screen. Grant access and the server will save credentials automatically.

When tokens expire, any tool call will return the /auth URL. Click it to re-authenticate — no container restart needed.

Option B: Environment Variable (Fallback)

If you prefer static credentials or can't expose a callback URL, set GSC_REFRESH_TOKEN in your env file. See the manual OAuth flow below.

Manual OAuth flow

export GSC_CLIENT_ID="your_client_id_here"
exp

... [View full README on GitHub](https://github.com/crunchtools/mcp-google-search-console#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

78/100across 5 weighted dimensions

How we score →

0255075100

−22

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked mcp-google-search-console-crunchtools against OSV.dev.

Inventory

Tools (10)

Click any tool to inspect its schema.

~805 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Google Search Console MCP Server safe to use?: Google Search Console MCP Server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under AGPL-3.0.
How do I install Google Search Console MCP Server?: Google Search Console MCP Server supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can Google Search Console MCP Server do?: Google Search Console MCP Server provides 10 tools: list_sites, get_site, add_site, delete_site, query_search_analytics and 5 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Google Search Console MCP Server?: Google Search Console MCP Server is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Is Google Search Console MCP Server actively maintained?: Google Search Console MCP Server is recently maintained — last commit was 40 days ago.