SEO Analytics MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_GSC_SITE_URL | Yes | Default Google Search Console site URL. Required format: sc-domain:example.com | |
| DEFAULT_GA4_PROPERTY_ID | Yes | Default Google Analytics 4 property ID |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capabilitiesB | Show enabled connectors, defaults, and key analysis thresholds. |
| gsc_list_sitesB | List Search Console properties available to the authenticated account. |
| gsc_search_analytics_rawC | Run a raw Search Console Search Analytics query with full options. |
| gsc_top_pagesC | Return top pages from GSC with clicks, impressions, CTR, and position. |
| gsc_top_queriesC | Return top queries from GSC by clicks. |
| gsc_query_page_pairsC | Return query+page combinations from GSC for intent/page matching analysis. |
| ga4_run_report_rawC | Run raw GA4 report with optional dimension/metric filters and ordering. |
| ga4_landing_pagesC | Return GA4 landing pages with engagement and conversion metrics. |
| ga4_channel_reportC | Break down GA4 landing pages by default channel group. |
| analytics_merge_page_metricsC | Merge normalized GSC + GA4 page metrics into one dataset. |
| analytics_generate_action_itemsC | Generate prioritized SEO and content action items from merged data. |
| analytics_popularity_snapshotC | Get top pages by clicks, impressions, sessions, and conversions. |
| analytics_trend_reportC | Compare current vs previous period to surface gainers and decliners. |
| analytics_data_quality_reportC | Show merge coverage and top URL mismatches between GSC and GA4. |
| analytics_query_page_opportunitiesC | Find high-impression query/page pairs with weak CTR and weak on-page outcomes. |
| analytics_topic_clustersC | Extract high-impact query token clusters to guide content focus. |
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 16 tools
Most tools have distinct purposes, such as merging data, generating reports, or querying specific platforms. However, some overlap exists between analytics tools like 'analytics_popularity_snapshot' and 'gsc_top_pages', which could cause confusion in selection for similar tasks.
The naming is mixed, with prefixes like 'analytics_', 'ga4_', and 'gsc_' used consistently within groups, but the overall pattern is not uniform. Tools like 'capabilities' break the verb_noun convention, and there is no single naming style across all tools.
With 16 tools, the count is slightly high but reasonable for an SEO analytics domain that covers data merging, reporting, and platform-specific queries. It provides comprehensive coverage without being overly bloated.
The tool set offers complete coverage for SEO analytics, including data integration from GSC and GA4, trend analysis, opportunity identification, and action item generation. There are no obvious gaps, supporting end-to-end workflows effectively.