GA4 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GA4_PROPERTY_ID | Yes | Your GA4 property ID (numeric, e.g., 544866887) | |
| GA4_CREDENTIALS_PATH | Yes | Path to the GA4 service account JSON file (e.g., ./credentials.json) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_traffic_summaryA | Get overall traffic summary for a date range (sessions, users, page views, bounce rate, avg session duration) |
| get_top_pagesB | Get top pages by views for a date range |
| get_traffic_sourcesB | Get traffic breakdown by source (organic, direct, referral, etc.) |
| get_user_engagementC | Get user engagement metrics (engaged sessions, bounce rate, avg session duration, screens per session) |
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 4 tools
Each tool targets a distinct aspect of GA4: top pages, traffic sources, overall traffic summary, and user engagement. No overlapping purposes.
All tools follow a consistent verb_noun pattern ('get_<metric_group>'), making them predictable and easy to navigate.
With 4 tools, the set is lean but covers core reporting needs. Slightly under-scoped for a full analytics server, but still reasonable.
Covers basic traffic, pages, sources, and engagement, but missing key GA4 reports like events, conversions, and user demographics, limiting agent capabilities.