Google Analytics MCP

Calls the GA4 Admin API to list accessible accounts and properties as native account summaries. A follow-up fetches one property's configuration, including reporting timezone and currency. A data-streams lookup lists web and app streams for a property, including available website URLs.

Retrieves session acquisition grouped by channel, source/medium or campaign with native GA4 metrics. A first-user acquisition tool describes the original channel rather than the source of subsequent sessions. Both tools return native GA4 attribution and differ from event-scoped metrics.

Sends a Core report request with your chosen dimensions, metrics, filters and date range, returning one bounded page of native results with headers and optional aggregates. Compatibility checking runs by default to confirm the dimension and metric combination is valid before the query executes.

Retrieves observed event names and counts for explicit dates with optional event filtering. A key-events tool lists the conversions configured on the property. Event counts are not unique sessions; use a report with session metrics to connect events to sessions.

Runs the same report recipe for up to six named date ranges, returning independent result sets without calculating differences. A time-series tool groups native metrics by day, week, month or hour in the property's reporting timezone, with missing intervals left as missing.

Discover accessible Google Analytics accounts and properties as native account summaries. Page size counts account summaries, each of which can contain multiple property summaries.

Get one GA4 property’s native configuration, including available reporting timezone and currency. This does not change settings.

List one GA4 property’s web and app streams, including available website URLs. Stream discovery helps select a site scope; it does not prove an exact GSC property match.

Discover standard, custom and comparison metadata for a GA4 property. Returns a bounded, optionally filtered catalog; comparison queries are outside v1.

List configured GA4 key events and native configuration. Current registration does not establish when an event was tracked or its historical counts.

Check Core report dimensions, metrics and filters; optionally list compatible additions. This endpoint does not validate funnel or realtime reports and does not guarantee data access or nonempty results.

Retrieve one bounded page of a GA4 Core report with native headers, numeric strings, restrictions and optional aggregates. Core compatibility checking is enabled by default and adds one read; pagination is not a snapshot.

Retrieve dimensionless native GA4 totals for explicit dates and filters. Never sum users across detail rows or average their rates; dimension filters still define the selected population.

Retrieve native GA4 metrics grouped by day, week, month or hour in the property reporting timezone. Missing intervals remain missing.

Retrieve ordered native GA4 funnel aggregates with explicit step, entry and sequence constraints. Uses the Alpha API; capped reports have no offset continuation and require a narrower request.

Retrieve landing-page traffic and engagement for Google organic sessions by default, or explicitly all organic search. Preserve native page identifiers; URL alignment with GSC belongs to the client.

Retrieve separate landing-page traffic context, selected event counts and optional native event-specific key-event rates. At most three report datasets; event filtering never narrows the context or rate denominator.

Retrieve session acquisition by channel, source/medium or campaign with selected native metrics. This differs from first-user acquisition and event-scoped attribution.

Retrieve native first-user acquisition groups and compatible metrics. Describes original acquisition rather than the source of subsequent sessions.

Retrieve observed event names and native counts/user metrics for explicit dates and optional event selection. Event occurrences are not unique converting sessions or configured key-event discovery.

Retrieve native metrics by country or device category with explicit traffic scope. Returns recorded aggregates without evaluating audience quality.

Retrieve independent native totals, daily trend and landing-page datasets, optionally session channels. At most four report datasets; no calculated summary or cross-dataset join.

Retrieve the same Core report recipe for up to six named periods. Returns independent datasets and continuations without calculating differences or matching absent rows.

Retrieve the same Core report recipe for up to six GA4 properties. Preserve each property’s scope, result and failure; never combine users or silently normalize currencies.

Yes, every GA4 property your connected Google account has at least Viewer access to. Properties are returned as native account summaries; Universal Analytics properties are not supported. Use the property ID (a numeric string like 123456789) in subsequent queries.

No. Every tool is read-only. The toolkit connects with the analytics.readonly OAuth scope, which does not permit creating or modifying properties, events, audiences or any configuration. Nothing in your Google Analytics account is changed.

GA4 data processing typically completes within 24–48 hours. Intraday data is available but may be partial. The toolkit returns what the GA4 Data API reports at query time, including any sampling Google applies to large datasets.

It cannot create or modify properties, event parameters, audiences, conversions or data streams. It does not support Universal Analytics, BigQuery exports, realtime reports, or cohort analysis (those tools are deferred). Results are bounded by GA4's own quotas and sampling thresholds.

Templates are included with Typenode. Each workflow that starts uses one run from your plan, including workflows called through your custom MCP connector. Third-party services may charge separately; see Apps and setup.

You choose which accounts to connect. The template’s workflows and tools use the access you configure. Review the required scopes and setup details before connecting an account.