Skip to main content
Glama
andrewjpyle

Google Search Console MCP

by andrewjpyle

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_SEARCH_CONSOLE_CLIENT_IDNoOAuth2 client ID
GOOGLE_SEARCH_CONSOLE_SITE_URLSYesComma-separated list of Google Search Console properties (first entry is default)
GOOGLE_SEARCH_CONSOLE_CREDENTIALSNoService account credentials JSON (full JSON on one line)
GOOGLE_SEARCH_CONSOLE_CLIENT_SECRETNoOAuth2 client secret
GOOGLE_SEARCH_CONSOLE_REFRESH_TOKENNoOAuth2 refresh token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
test_connectionB

Test connection and authentication to the Google Search Console API

list_sitesA

List all verified sites in the authenticated Search Console account

get_site_infoA

Get details and permission level for a specific verified site

search_analyticsB

Query Search Analytics data (clicks, impressions, CTR, position) by dimension

get_top_queriesC

Get the top search queries for a site over a lookback window

get_top_pagesA

Get the top performing pages for a site over a lookback window

list_sitemapsB

List all sitemaps submitted for a site

submit_sitemapA

Submit (or resubmit) a sitemap to Search Console — a real write operation

get_indexing_statusA

Inspect a URL with the URL Inspection API (index status, coverage, canonical, richness)

request_indexingB

Notify Google of a new or updated URL via the Web Search Indexing API — a real write operation

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but get_top_queries and get_top_pages overlap heavily with search_analytics since they are likely convenience wrappers around the same Analytics API. Agents could misselect between these, though descriptions help clarify the intent.

Naming Consistency4/5

Tool names mostly follow a consistent verb_noun pattern like list_sites, get_site_info, submit_sitemap. The main deviation is search_analytics, which is a noun phrase rather than get_ or list_ style, creating a minor inconsistency.

Tool Count5/5

10 tools is well-scoped for a Google Search Console MCP server. Each tool covers a meaningful area of the API—sites, search analytics, indexing, sitemaps, and connection testing—without unnecessary bloat or redundancy.

Completeness4/5

The tool set covers the primary Search Console workflows: site verification inspection, analytics queries, sitemap management, and indexing requests. Minor gaps exist such as no delete/remove sitemap or explicit URL removal tool, but these are not core workflows for most users.

Maintenance

ActivityMaintained
ResponsivenessNo issues