getActiveUsers
Get active users metrics for a specific date range
LABSCO SUMMARY
The four questions people actually ask GA4 are already tools, so you stop composing requests to answer them.
getPageViews, getActiveUsers, getEvents and getUserBehavior each take a date range and nothing else, which covers the routine reads without a trip through the report builder; runReport is there for the ones that do not fit. Everything is read-only, and the property is fixed by GA_PROPERTY_ID rather than passed per call — no tool here takes a property identifier, so a second property means a second server.
What it is
Five read tools over a single GA4 property: four preset reports covering the routine questions, and runReport for anything you can express as metrics plus dimensions plus a dimension filter.
What you get
- Page view metrics for a date range, optionally broken out by dimensions you name
- Active users for a date range
- Event metrics for a date range, narrowed to a single eventName when you pass one
- Session duration and bounce rate for a date range
- Any report expressible as metrics, dimensions and a dimensionFilter, through runReport
Requirements
A GA4 property and a Google service account authorised on it: GOOGLE_CLIENT_EMAIL, GOOGLE_PRIVATE_KEY and GA_PROPERTY_ID.
Setup effort
One command plus credentials — npm install -g mcp-server-google-analytics, then supply credentials
USE CASES
01
Answering "how did the site do last month"
Two calls over the same date range give traffic and audience: page views, optionally split by dimensions, and the active user count.
02
Checking whether a newly instrumented event is firing
Name the event and a date range that starts at the release, and see whether anything came back at all — the fastest way to tell a tracking bug from a product problem.
03
Looking at engagement rather than volume
Session duration and bounce rate over a date range answer whether the traffic you got was the traffic you wanted.
04
Building the report the presets do not cover
Specify metrics, dimensions and a dimension filter directly when the question is narrower than the four preset reports — a landing page cohort, one campaign, one country.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
getEvents
Get event metrics for a specific date range
getPageViews
Get page view metrics for a specific date range
getUserBehavior
Get user behavior metrics like session duration and bounce rate
runReport
Run a report to get analytics data
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. All five only read GA4. runReport is the general tool; the other four are presets. Names are camelCase, such as getPageViews.
Requires
- npx on PATH
- Node.js 20 or later
- GOOGLE_CLIENT_EMAIL in your environment
- GOOGLE_PRIVATE_KEY in your environment
- GA_PROPERTY_ID in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g mcp-server-google-analyticsMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"google-analytics": {
"command": "npx",
"args": [
"-y",
"mcp-server-google-analytics"
],
"env": {
"GOOGLE_CLIENT_EMAIL": "<YOUR_GOOGLE_CLIENT_EMAIL>",
"GOOGLE_PRIVATE_KEY": "<YOUR_GOOGLE_PRIVATE_KEY>",
"GA_PROPERTY_ID": "<YOUR_GA_PROPERTY_ID>"
}
}
}
}
