mcp-site-analyst
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Bearer token for HTTP mode authentication. | |
| GOOGLE_CREDENTIALS_JSON | No | Full JSON key as a string for Google service account credentials. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to the Google service account key file. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ga4_run_reportA | Run a custom GA4 report with flexible dimensions, metrics, and date ranges. Use ga4_get_metadata to discover available dimensions and metrics first. |
| ga4_realtime_reportA | Get real-time active users and metrics from GA4. Shows data from the last 30 minutes. |
| ga4_get_metadataA | List all available dimensions and metrics for a GA4 property. Use this to discover what fields are available before running reports. |
| ga4_top_pagesA | Get the top pages by page views for a GA4 property. A convenient shortcut for a common report. |
| ga4_top_traffic_sourcesA | Get top traffic sources for a GA4 property, broken down by source/medium. |
| ga4_user_demographicsA | Get user demographics breakdown (country, city, or language) for a GA4 property. |
| gsc_search_analyticsB | Query Google Search Console search analytics data. Returns clicks, impressions, CTR, and average position. Can be broken down by query, page, country, device, or date. |
| gsc_list_sitemapsA | List all sitemaps submitted to Google Search Console for a site. |
| gsc_get_sitemapB | Get detailed information about a specific sitemap. |
| gsc_inspect_urlA | Inspect a URL in Google Search Console. Returns indexing status, crawl info, mobile usability, and rich results status. Note: daily quotas apply. |
| gsc_list_sitesA | List all sites the service account has access to in Google Search Console. |
| gsc_top_queriesB | Get top search queries by clicks for a site. A convenient shortcut for common analysis. |
| gsc_top_pagesB | Get top pages by clicks in Google Search for a site. A convenient shortcut. |
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 13 tools
Tools are cleanly separated by service prefix (ga4_ vs gsc_) and each targets a distinct function. Even the top_pages tools are unambiguous because one is GA4 page views and the other is GSC search clicks, with clear descriptions noting they are conveniences over more general reporting tools.
All tools follow a consistent lower_snake_case pattern with service prefixes, and the action or data focus is clear. While some names omit explicit verbs (e.g., ga4_top_pages), the pattern is uniform across the set, making it easy to infer behavior.
13 tools is well within the ideal range for a focused analytics server, covering both GA4 and GSC without redundancy. Each tool earns its place by providing a distinct, useful capability for site analysis.
The tool surface covers core analytics needs for both GA4 (demographics, realtime, custom reports, metadata, common metrics) and GSC (search performance, sitemaps, URL inspection, site listing). Minor gaps exist, such as no explicit GA4 property listing or advanced GSC sitemap submission, but these do not block typical analysis workflows.