Web Analytics & Tracking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GA4_API_SECRET | No | GA4 Measurement Protocol API secret | |
| GA4_MEASUREMENT_ID | No | Google Analytics 4 Measurement ID (e.g., G-XXXXXXXXXX) |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_datalayer_eventB | Validates a GTM DataLayer event payload against GA4 & E-commerce schema standards to detect missing parameters or invalid types. |
| send_ga4_measurement_protocol_eventB | Transmits a server-side analytics event to Google Analytics 4 via Measurement Protocol API. |
| generate_tracking_code_snippetA | Generates production-ready tracking code snippets for GTM dataLayer.push, GA4 gtag.js, or React custom hook. |
| audit_tracking_readinessA | Audits a tracking event payload against GA4 or Meta CAPI readiness standards and returns an EMQ/Quality score (0-100) with actionable recommendations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ga4-ecommerce-spec |
TDQS
Scored across 4 tools
The tools are mostly distinct: generating, validating, auditing, and sending events each serve clear purposes. However, 'audit_tracking_readiness' and 'validate_datalayer_event' both involve checking payloads, which could cause some confusion despite their different scopes (readiness/score vs schema validation).
All tool names follow a consistent verb_noun pattern in snake_case: audit, generate, validate, and send. The naming is predictable and clearly indicates the action being performed.
With only 4 tools, the server is tightly scoped to its purpose of web analytics tracking. Each tool covers a distinct aspect (generation, validation, auditing, server-side sending), so the count feels appropriate without being too thin or heavy.
The tool surface covers the primary workflow for implementing and verifying tracking: generate code, validate payloads, audit readiness, and send events. Minor gaps exist, such as no direct tool for fetching schemas or managing tracking configuration, but these are not critical for the core use case.