Google Analytics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GA4_PROPERTY_ID | Yes | Numeric property ID from GA4 Admin -> Property Settings (e.g. 123456789). Not the Measurement ID (G-XXXXXXX). | |
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Absolute path to the service account JSON 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ga4_run_reportA | Flexible GA4 Data API runReport. Pass any dimensions + metrics. Use for custom reports the preset tools don't cover. |
| ga4_organic_search_performanceA | SEO: sessions/users/engagement/conversions for Organic Search traffic, broken down by landing page (default), source, country, or device. |
| ga4_paid_search_performanceB | Paid: sessions/conversions/cost/CPC for Paid Search traffic, broken down by campaign (default), landing page, keyword, or source. |
| ga4_all_paid_performanceA | Paid: all paid channels (Search + Social + Video + Display + Other) broken down by channel × campaign × source × medium, with cost and ROAS. |
| ga4_google_ads_performanceA | Paid: Google Ads campaign × ad group × keyword performance (impressions, clicks, cost, CPC, conversions, ROAS). Requires Google Ads ↔ GA4 link. |
| ga4_landing_page_performanceA | Top landing pages by sessions/engagement/conversions. Optional channel filter (e.g. 'Organic Search', 'Paid Search'). |
| ga4_channel_performanceB | Default channel group rollup: sessions/users/conversions/revenue for Organic Search, Paid Search, Email, Direct, Referral, etc. |
| ga4_campaign_performanceB | Campaign × source × medium breakdown with sessions/conversions/revenue. Optional channel filter. |
| ga4_conversions_by_sourceB | Conversions and key events broken down by session source × medium × channel group. Sorted by key events desc. |
| ga4_realtime_active_usersB | Current active users (last 30 min) broken down by screen/page, country, device, or audience. |
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 10 tools
Each tool targets a distinct area of GA4 data: all paid, specific channels, campaigns, conversions, landing pages, organic/paid search, realtime, and a generic report. No two tools have overlapping purposes that would cause confusion.
All tool names consistently follow the 'ga4_<descriptive_name>' format using snake_case. The naming pattern is predictable and uniform across the entire set.
10 tools is well within the ideal 3-15 range for a focused analytics server. Each tool serves a clear purpose, and the count feels neither excessive nor insufficient for covering core GA4 queries.
The set covers acquisition, behavior, conversions, and realtime analytics well. Minor gaps exist (e.g., user demographics, event details), but the flexible ga4_run_report tool allows agents to fill these gaps for custom reports.