Google Analytics 4
io.github.stucchiPublished by GitHub account stucchiv0.1.1Updated Oct 24, 2026
Manage GA4 properties, data streams, conversions, and run reports via Admin & Data APIs.
Overview
MCP server for Google Analytics 4 that lets an assistant manage GA4 properties, data streams and conversions and run reports via the Admin and Data APIs.
- What you can do
- Check authentication status of the configured service account
- List accounts and properties, create, inspect and soft-delete properties
- List, create and delete web data streams and generate the gtag.js tracking snippet
- List, create and delete key events (conversions), custom dimensions and custom metrics
- List and create Google Ads links, and get or create a Measurement Protocol secret
- Run reports and real-time reports with dimensions, metrics, dates and filters, and list available dimensions and metrics
- When to use it
- Useful when you want an assistant to set up GA4 tracking for a site, adjust conversions or custom dimensions, or pull session, country and real-time metrics without opening the GA4 interface.
- Requirements
- Runs locally as a PyPI package (google-analytics-4-mcp) launched via uvx, so Python tooling is needed. Requires a Google Cloud service account JSON key supplied through GA_CREDENTIALS or GA_CREDENTIALS_PATH, the Analytics Admin and Data APIs enabled in that project, and the service account email added as Editor in GA4 property access management.
Installation
In SourceWeft
- Open Google Analytics 4 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Google Analytics 4 MCP Server
MCP server for Google Analytics 4 — create properties, configure data streams, manage conversions, and run reports via the Admin & Data APIs.
Setup (one-time, ~3 minutes)
-
Google Cloud Console → IAM & Admin → Service Accounts
- Create a service account (any name)
- Click it → Keys → Add Key → JSON → Download
-
Enable APIs in your GCP project:
-
GA4 Admin → Property Access Management → Add the service account email (from the JSON) as Editor
-
Configure credentials (pick one):
- Option A (recommended): Copy the JSON content into the
GA_CREDENTIALSenv var in your MCP config - Option B: Save the file to
~/.google-analytics-4-mcp/credentials.json
- Option A (recommended): Copy the JSON content into the
Done. No browser flow, no consent screen, no tokens to refresh.
Installation
Claude Code
Claude Desktop
Add to claude_desktop_config.json:
From source
Getting Started
- Check auth: Call
check_auth_statusto verify the service account is configured - List accounts: Call
list_accountsto see your GA4 accounts - Setup a property: Use
create_property→create_web_data_stream→get_tracking_snippet - Query data: Use
run_reportwith dimensions and metrics
Tools (23)
Auth
Admin API
Data API
Environment Variables
GA_CREDENTIALS takes priority over GA_CREDENTIALS_PATH.
Example Usage
License
MIT
Source: README.md at commit bb4b629
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.