# io.github.leonardosepulvedat/mcp-google-analytics (npm · mcp-google-analytics)

GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `mcp-google-analytics`: 81/100 (this document), [markdown](https://verifymcp.io/servers/leonardosepulvedat-mcp-google-analytics/mcp-google-analytics.md), [page](https://verifymcp.io/servers/leonardosepulvedat-mcp-google-analytics/mcp-google-analytics)

## Channel facts

- Registry: `npm`
- Package: `mcp-google-analytics`
- Version: `1.3.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 44 of 130 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 29 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2891 tokens (~111/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ga_send_event" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.leonardosepulvedat/mcp-google-analytics server?

io.github.leonardosepulvedat/mcp-google-analytics runs locally as an npm package, launched with npx -y mcp-google-analytics. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add leonardosepulvedat-mcp-google-analytics -- npx -y mcp-google-analytics
```

### Cursor

```json
{
  "mcpServers": {
    "leonardosepulvedat-mcp-google-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-analytics"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "leonardosepulvedat-mcp-google-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-analytics"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add leonardosepulvedat-mcp-google-analytics -- npx -y mcp-google-analytics
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "leonardosepulvedat-mcp-google-analytics": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-google-analytics"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add leonardosepulvedat-mcp-google-analytics --command npx --arg -y --arg mcp-google-analytics
```

### Hermes

```yaml
mcp_servers:
  leonardosepulvedat-mcp-google-analytics:
    command: "npx"
    args: ["-y", "mcp-google-analytics"]
```

### Netclaw

```json
{
  "McpServers": {
    "leonardosepulvedat-mcp-google-analytics": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-google-analytics"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add leonardosepulvedat-mcp-google-analytics -t stdio -c npx -a -y mcp-google-analytics
```

### Other

```json
{
  "mcpServers": {
    "leonardosepulvedat-mcp-google-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-analytics"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 81, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (26)

### `ga_run_report` (~258 tokens)

Run a custom Google Analytics report with dimensions and metrics.

⚠️ TOKEN OPTIMIZATION: Use 'limit' to control result size (default: 10).
This tool can consume significant tokens with large datasets.

Common dimensions: date, city, country, deviceCategory, browser, pagePath, eventName
Common metrics: activeUsers, sessions, screenPageViews, conversions, totalRevenue

Input parameters:

- `dateRanges` (array, required): Date ranges for the report
- `dimensionFilter` (object): Dimension filter expression
- `dimensions` (array): Dimensions to group by (e.g., [{name: "date"}])
- `limit` (integer): Maximum number of rows to return (default: 10)
- `metricFilter` (object): Metric filter expression
- `metrics` (array, required): Metrics to measure (e.g., [{name: "activeUsers"}])
- `offset` (integer): Number of rows to skip (for pagination)
- `orderBys` (array): Sorting specification
- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_run_realtime_report` (~156 tokens)

Get real-time Google Analytics data (last 30 minutes).

⚠️ TOKEN OPTIMIZATION: Use 'limit' to control result size (default: 10).

Common dimensions: city, country, deviceCategory, unifiedScreenName
Common metrics: activeUsers, screenPageViews, conversions

Input parameters:

- `dimensions` (array): Dimensions to group by
- `limit` (integer): Maximum number of rows (default: 10)
- `metrics` (array, required): Metrics to measure
- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_get_metadata` (~103 tokens)

Get available dimensions and metrics metadata for your GA4 property.

⚠️ TOKEN OPTIMIZATION: This returns ALL available dimensions and metrics.
Response can be large (~500+ items). Use sparingly and cache results when possible.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_list_accounts` (~30 tokens)

List all Google Analytics accounts accessible to the service account.

Use this to find account IDs for listing properties.

### `ga_list_properties` (~57 tokens)

List Google Analytics properties.

Optionally filter by account ID. Without an account ID, properties from all
accessible accounts are aggregated.

Input parameters:

- `accountId` (string): Optional account ID to filter properties (e.g., "123456789")

### `ga_get_property` (~77 tokens)

Get details about a GA4 property (the configured one, or any accessible property via propertyId).

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_list_data_streams` (~79 tokens)

List data streams for the configured GA4 property.

Use this to find measurement IDs for Measurement Protocol.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_run_pivot_report` (~137 tokens)

Run a pivot table report with row and column dimensions.

⚠️ TOKEN OPTIMIZATION: Pivot reports can be VERY large.
Limit dimensions and use small date ranges. Recommended for analysis, not raw data extraction.

Input parameters:

- `dateRanges` (array, required)
- `dimensions` (array)
- `metrics` (array, required)
- `pivots` (array, required): Pivot specifications with fieldNames
- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_run_funnel_report` (~154 tokens)

Run a funnel analysis report to track user progression through steps (Data API v1alpha).

Each step matches an event: set 'eventName' per step (defaults to the step name).
For advanced matching, pass a full 'filterExpression' instead.

Input parameters:

- `dateRanges` (array, required)
- `funnelBreakdown` (object): Optional dimension to break down funnel
- `funnelSteps` (array, required): Steps in the funnel
- `funnelVisualizationType` (string)
- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_batch_run_reports` (~116 tokens)

Run multiple reports in a single request.

⚠️ TOKEN OPTIMIZATION: Can return LARGE amounts of data.
Limit to 2-5 reports per batch. Each report should have small limits.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.
- `requests` (array, required): Array of report requests (same format as ga_run_report)

### `ga_get_account_summaries` (~44 tokens)

Get a compact overview of all accessible GA accounts and their properties in a single call.

The fastest way to discover account IDs, property IDs, and property names.

### `ga_list_custom_dimensions` (~92 tokens)

List all custom dimensions defined for the configured GA4 property.

Use this to discover custom dimension API names (e.g., "customEvent:plan_type") for reports.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_list_custom_metrics` (~81 tokens)

List all custom metrics defined for the configured GA4 property.

Use this to discover custom metric API names for reports.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_list_key_events` (~89 tokens)

List the key events (conversions) configured for the GA4 property.

Useful to know which event names count as conversions before building reports or sending events.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_list_google_ads_links` (~70 tokens)

List Google Ads accounts linked to a GA4 property.

Input parameters:

- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_check_compatibility` (~161 tokens)

Check whether a combination of dimensions and metrics is valid for this property BEFORE running a report.

Avoids wasted report requests and token-heavy error loops. Also lists which other fields remain compatible with the given combination.

Input parameters:

- `compatibilityFilter` (string): Only return fields with this compatibility (recommended: COMPATIBLE)
- `dimensions` (array): Dimensions to check (e.g., [{name: "city"}])
- `metrics` (array): Metrics to check (e.g., [{name: "activeUsers"}])
- `propertyId` (string): GA4 property ID to query (overrides the default GA_PROPERTY_ID). Accepts "123456789" or "properties/123456789". Use ga_get_account_summaries to discover IDs.

### `ga_send_event` (~141 tokens)

Send a custom event to Google Analytics via Measurement Protocol.

Use this for tracking custom user actions, conversions, or any GA4 event.
Events are processed asynchronously and appear in reports within minutes.

Common events: click, form_submit, video_play, file_download, custom_conversion

Input parameters:

- `client_id` (string): Client ID (UUID format recommended). Auto-generated if not provided.
- `events` (array, required): Events to send (can send multiple in one request)
- `user_id` (string): Optional User ID for cross-device tracking
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})

### `ga_validate_event` (~90 tokens)

Validate an event before sending it to Google Analytics.

Uses GA4's debug endpoint to check for errors without recording the event.
Returns validation messages and errors if any.

Input parameters:

- `client_id` (string)
- `events` (array, required)
- `user_id` (string)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})

### `ga_send_pageview` (~124 tokens)

Send a page view event to Google Analytics.

Standard event for tracking page/screen views. Automatically uses 'page_view' event name.

Input parameters:

- `client_id` (string): Client ID (auto-generated if not provided)
- `page_location` (string, required): Full URL of the page
- `page_referrer` (string): Referrer URL
- `page_title` (string): Page title
- `user_id` (string): Optional User ID
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})

### `ga_send_purchase` (~155 tokens)

Send an ecommerce purchase event to Google Analytics.

Standard event for tracking completed purchases with transaction details and items.

Input parameters:

- `affiliation` (string): Store or affiliation
- `client_id` (string)
- `coupon` (string): Coupon code used
- `currency` (string, required): Currency code (e.g., USD, EUR)
- `items` (array, required): Purchased items
- `shipping` (number): Shipping cost
- `tax` (number): Tax amount
- `transaction_id` (string, required): Unique transaction ID
- `user_id` (string)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})
- `value` (number, required): Total purchase value

### `ga_send_login` (~97 tokens)

Send a login event to Google Analytics.

Standard event for tracking user logins with authentication method.

Input parameters:

- `client_id` (string)
- `method` (string, required): Login method (e.g., "Google", "Email", "Facebook")
- `user_id` (string): User ID (recommended for login events)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})

### `ga_send_signup` (~92 tokens)

Send a sign-up event to Google Analytics.

Standard event for tracking new user registrations.

Input parameters:

- `client_id` (string)
- `method` (string, required): Sign-up method (e.g., "Google", "Email")
- `user_id` (string): User ID for the new user
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})

### `ga_send_add_to_cart` (~107 tokens)

Send an add to cart event to Google Analytics.

Ecommerce event for tracking when items are added to shopping cart.

Input parameters:

- `client_id` (string)
- `currency` (string, required): Currency code
- `items` (array, required): Items added to cart
- `user_id` (string)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})
- `value` (number, required): Total value of items added

### `ga_send_begin_checkout` (~112 tokens)

Send a begin checkout event to Google Analytics.

Ecommerce event for tracking when users start the checkout process.

Input parameters:

- `client_id` (string)
- `coupon` (string): Coupon code applied
- `currency` (string, required): Currency code
- `items` (array, required): Items in checkout
- `user_id` (string)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})
- `value` (number, required): Total value of cart

### `ga_send_view_item` (~121 tokens)

Send a view item event to Google Analytics.

Ecommerce event for tracking product/item detail views. Completes the standard
funnel: view_item → add_to_cart → begin_checkout → purchase.

Input parameters:

- `client_id` (string)
- `currency` (string, required): Currency code
- `items` (array, required): Items viewed
- `user_id` (string)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})
- `value` (number, required): Value of the viewed item(s)

### `ga_send_refund` (~148 tokens)

Send a refund event to Google Analytics.

Ecommerce event for full or partial refunds. Omit 'items' for a full refund;
include them (with quantities) for a partial refund. Use the same transaction_id
as the original purchase.

Input parameters:

- `client_id` (string)
- `currency` (string): Currency code
- `items` (array): Refunded items (only for partial refunds)
- `transaction_id` (string, required): Transaction ID of the original purchase
- `user_id` (string)
- `user_properties` (object): User properties (e.g., {subscription_tier: {value: "premium"}})
- `value` (number): Refunded amount

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/leonardosepulvedat-mcp-google-analytics/mcp-google-analytics#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 67
- 2026-08-27: 67
- 2026-08-26: 67
- 2026-08-25: 67
- 2026-08-24: 67
- 2026-08-23: 67
- 2026-08-22: 67

## Common questions

### What is the io.github.leonardosepulvedat/mcp-google-analytics server?

io.github.leonardosepulvedat/mcp-google-analytics is listed in the public MCP registry as io.github.leonardosepulvedat/mcp-google-analytics. GA4 MCP that reads AND writes: reports, funnels, audits, and server-side events. 26 tools. This page covers its npm package (mcp-google-analytics).

### Is the io.github.leonardosepulvedat/mcp-google-analytics server safe to use?

io.github.leonardosepulvedat/mcp-google-analytics scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.leonardosepulvedat/mcp-google-analytics server expose?

io.github.leonardosepulvedat/mcp-google-analytics exposes 26 tools: ga_run_report, ga_run_realtime_report, ga_get_metadata, ga_list_accounts, ga_list_properties, and 21 more. Their descriptions and schemas cost roughly 2,891 tokens of context every time the server is loaded.

### Is the io.github.leonardosepulvedat/mcp-google-analytics server still maintained?

io.github.leonardosepulvedat/mcp-google-analytics is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.leonardosepulvedat/mcp-google-analytics server under?

io.github.leonardosepulvedat/mcp-google-analytics declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mcp-google-analytics
- Socket report: https://socket.dev/npm/package/mcp-google-analytics
- Repository: https://github.com/leonardosepulvedat/mcp-google-analytics
- Changelog RSS feed: https://verifymcp.io/servers/leonardosepulvedat-mcp-google-analytics/mcp-google-analytics.xml
- Changelog JSON feed: https://verifymcp.io/servers/leonardosepulvedat-mcp-google-analytics/mcp-google-analytics.json
- HTML version of this page: https://verifymcp.io/servers/leonardosepulvedat-mcp-google-analytics/mcp-google-analytics