gsc-ga4-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_mappingsB | List local domain/client mappings from PROJECTS_CONFIG. |
| project_lookupB | Find a local project mapping by project name, client, or domain. |
| gsc_list_sitesA | List Google Search Console sites visible to the current credentials. |
| gsc_search_analyticsD | Run a raw Search Console Search Analytics query. |
| gsc_top_queriesC | Top GSC queries by clicks/impressions. |
| gsc_top_pagesC | Top GSC pages by clicks/impressions. |
| gsc_query_page_matrixC | GSC query/page matrix for finding page-level keyword opportunities. |
| gsc_url_inspectionA | Inspect Google index status for a URL under a GSC property. |
| ga4_list_propertiesA | List GA4 accounts and property summaries visible to the credentials. |
| ga4_run_reportC | Run a raw GA4 Data API report. |
| ga4_top_pagesC | Top GA4 pages by views, users, and sessions. |
| ga4_traffic_sourcesB | GA4 traffic sources by default channel group and source/medium. |
| ga4_landing_pagesD | GA4 landing pages with engagement metrics. |
| ga4_eventsC | GA4 events by event name. |
| ga4_realtimeD | GA4 realtime active users report. |
| find_high_impression_low_ctr_pagesC | Find GSC pages with high impressions and low CTR. |
| compare_gsc_ga4_pagesC | Join GSC page performance with GA4 landing-page engagement. |
| find_pages_with_clicks_but_low_engagementC | Find pages with GSC clicks but weak GA4 engagement. |
| content_refresh_candidatesC | Rank pages that may deserve a content refresh based on GSC opportunity and GA4 engagement. |
| seo_opportunity_reportC | Compact SEO opportunity report combining high-impression/low-CTR and low-engagement candidates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Several tools overlap heavily: gsc_search_analytics is a raw query tool but gsc_top_queries, gsc_top_pages, and gsc_query_page_matrix are just specialized versions of it. Similarly, ga4_run_report overlaps with ga4_top_pages, ga4_traffic_sources, ga4_landing_pages, and ga4_events, while the final four SEO opportunity tools substantially duplicate one another in purpose.
Naming is mostly consistent with service prefixes (gsc_, ga4_) followed by descriptive topic or verb_noun forms like list_sites and run_report. Minor inconsistencies exist, such as project_mappings/project_lookup using a different pattern and the verb-less gsc_search_analytics, but overall the convention is predictable.
20 tools is on the heavier side, but the server intentionally covers two analytics platforms plus cross-platform analysis, so the count is defensible. A few of the derived report tools are redundant enough that the set could be trimmed, but it does not feel bloated beyond reason.
The toolset covers the core read-only SEO workflow well: GSC site listing, raw and curated search analytics, URL inspection, GA4 property/report access, and cross-platform opportunity analysis. Minor gaps exist, such as no GSC sitemap or index-request tools and no GA4 audience or funnel reports, but the raw query tools provide a workaround.