Google Analytics MCP Server
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 |
|---|---|
| analytics_reportC | Get comprehensive Google Analytics data with custom dimensions and metrics. Can create any type of report. |
| realtime_dataC | Get real-time analytics data for current active users and activity |
| quick_insightsC | Get predefined analytics insights for common use cases |
| get_metadataA | Get available dimensions and metrics for Google Analytics property |
| search_metadataC | Search for specific dimensions or metrics by name or category |
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 5 tools
Each tool targets a distinct purpose: real-time data, comprehensive reports, metadata listing, predefined insights, and metadata search. No overlap, agent can easily differentiate.
Mostly snake_case with descriptive names, but mixes verb-noun (get_metadata, search_metadata) with noun-noun (realtime_data, analytics_report) and adjective-noun (quick_insights). Minor inconsistency but still clear.
5 tools is well-scoped for a Google Analytics server covering main data access needs: realtime, custom reports, metadata, insights, and search. Neither too few nor excessive.
Covers key Google Analytics data retrieval: real-time, custom reports via analytics_report (which can handle any dimensions/metrics), metadata listing, search, and predefined insights. No obvious gaps for a read-only analytics server.