Skip to main content
Glama
chrishart0

searchconsole-mcp

by chrishart0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_APPLICATION_CREDENTIALSNoPath to your Google Cloud service account key JSON file. This is recommended for automation and is used for authentication if you are not using system-level user credentials.

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_sitesA

Lists all verified properties in Google Search Console.

Returns site URLs and permission levels.

query_search_analyticsA

Query Google Search Console search analytics data.

This is the main keyword research tool. Returns rows with clicks,
impressions, CTR, and average position.

Args:
    site_url: The site URL as it appears in Search Console
        (e.g. "https://mychefai.com" or "sc-domain:mychefai.com").
    start_date: Start date in YYYY-MM-DD format.
    end_date: End date in YYYY-MM-DD format.
    dimensions: List of dimensions to group by. Options: query, page,
        date, country, device, searchAppearance. Defaults to ["query"].
    row_limit: Max rows to return (1-25000, default 1000).
    start_row: Starting row offset for pagination (default 0).
    dimension_filters: Optional list of filter objects. Each filter has:
        - dimension: the dimension to filter on (e.g. "query", "page")
        - operator: one of "contains", "equals", "notContains",
          "notEquals", "includingRegex", "excludingRegex"
        - expression: the filter value
        Example: [{"dimension": "query", "operator": "contains",
                    "expression": "keto"}]
    search_type: Type of search results. One of: web, image, video,
        news, discover, googleNews. Default "web".
    aggregation_type: How to aggregate results. One of: auto, byPage,
        byProperty. If omitted, the API auto-selects.
list_sitemapsB

Lists submitted sitemaps for a Search Console property.

Args:
    site_url: The site URL as it appears in Search Console
        (e.g. "https://mychefai.com" or "sc-domain:mychefai.com").

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: list_sitemaps handles sitemap management, list_sites provides property overview, and query_search_analytics focuses on search performance data. The descriptions reinforce these boundaries, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (list_sitemaps, list_sites, query_search_analytics) with clear, descriptive names. There are no deviations in style or convention across the set.

Tool Count3/5

With only 3 tools, the set feels thin for a Search Console MCP server, lacking operations like sitemap submission/deletion, property verification, or detailed configuration management. While the tools cover core areas, the scope seems limited compared to typical API capabilities.

Completeness2/5

The tool surface has significant gaps for Search Console functionality: no create/update/delete operations for sitemaps or properties, missing tools for URL inspection, mobile usability, or security issues, and incomplete coverage of the API's core features like indexing status or rich results testing.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources