Google Analytics 4 MCP server
Understand what happens after the click.
Explore traffic, conversions, funnels and property configuration through a read-only MCP server.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @getmcpads/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
GA4_CLIENT_ID=<value> GA4_CLIENT_SECRET=<secret> GA4_REFRESH_TOKEN=<secret> GA4_PROPERTY_ID=<value> GA4_PROPERTY_IDS=<value> claude mcp add com.getmcpads-google-analytics -- npx -y @getmcpads/google-analytics-mcp-server@2.1.2รันในเทอร์มินัล
{ "mcpServers": { "com.getmcpads-google-analytics": { "command": "npx", "args": [ "-y", "@getmcpads/[email protected]" ], "env": { "GA4_CLIENT_ID": "<value>", "GA4_CLIENT_SECRET": "<secret>", "GA4_REFRESH_TOKEN": "<secret>", "GA4_PROPERTY_ID": "<value>", "GA4_PROPERTY_IDS": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดThe film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.
27 read tools · Read-only by design.
Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.
v2.0.1: Native tools and security update · September 20, 2026
Requires Node.js 22.12 or newer. CI covers Node 22 and 24. Version 2.0.1 drops Node 18 and 20 support. Hosted creative integrations and MCP Apps UI are outside this release.
This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.
git clone --branch v2.0.1 --depth 1 https://github.com/get-mcp-ads/google-analytics-mcp-server.git
cd google-analytics-mcp-server
npm ci
npm run build
Configure your MCP client to run node with the absolute path to dist/cli.js and the platform credentials documented below.
Prefer a managed connection? Use Google Analytics 4 with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.
GA4 rejects many metric and dimension combinations, and its errors rarely explain which pair
is at fault. This server carries the compatibility matrix, so ga4_check_compatibility and
ga4_validate_query let the model verify a combination before spending a call and a quota
token on it.
Quotas matter here more than on ad platforms: GA4 charges tokens per property per day, and a
few careless exploratory queries can exhaust them. ga4_get_property_quotas_snapshot shows
what is left.
There are no write tools, and no environment variable that adds any. Every tool calls a read method of the Data API or the Admin API.
This is not caution for its own sake. A misread report is a wrong answer you can spot. A mistaken write to an analytics property, a deleted audience or an edited data stream, corrupts the record you use to judge everything else, and often silently. The other servers we publish do have write tools, guarded by a mandatory preview. This one has none.
Our ad platform servers with guarded writes: Meta Ads · Google Ads · TikTok Ads
Analytics data is not anonymous by default. A GA4 property can carry a userId you set
yourself, a device identifier, or a Google Signals pseudonymous ID. An MCP conversation sends
whatever a tool returns to a model.
Identifiers are redacted by default wherever this server can return them, and showing them is an explicit opt-in, never the default.
Every one of these accepts includePersonalIdentifiers: true to return raw values, and
defaults to false.
Audience export rows are positional, so the redaction reads the export's dimension metadata to find identifier columns. If that metadata is missing, every value in the row is redacted rather than guessing which column is safe. Failing closed is the point.
Report rows are not redacted. ga4_run_report and the other reporting tools return what
you asked for. Altering the numbers a report returns would be worse than returning them.
So one decision stays yours: if your property carries a userId you consider personal, do not
request it as a report dimension in a conversation whose transcript leaves your machine.
Three values, obtained once.
In a Google Cloud project, enable the Google Analytics Data API and the Google Analytics Admin API, then create an OAuth client under APIs & Services → Credentials. Choose Desktop app for local use. Note the client ID and client secret.
Run the OAuth consent flow once, signed in as a Google account with access to your GA4
properties, and keep the refresh token. The analytics.readonly scope is enough, and it
is the only one you should grant.
The refresh token does not expire. It is the sensitive value: anyone holding it can mint access tokens indefinitely. Use an OAuth client dedicated to this server so you can revoke it on its own.
Set GA4_PROPERTY_ID to avoid passing it on every call. Find it in GA4 under
Admin → Property Settings, or list them with ga4_list_properties.
Run ga4_health_check as your first call. It verifies the credentials and lists the
properties you can actually reach, without printing any secret.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"google-analytics": {
"command": "npx",
"args": ["-y", "@getmcpads/google-analytics-mcp-server"],
"env": {
"GA4_CLIENT_ID": "your-client-id",
"GA4_CLIENT_SECRET": "your-client-secret",
"GA4_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Restart Claude Desktop. Ask it: "list my Google Analytics properties".
claude mcp add google-analytics --env GA4_CLIENT_ID=... --env GA4_CLIENT_SECRET=... --env GA4_REFRESH_TOKEN=... -- npx -y @getmcpads/google-analytics-mcp-server
.cursor/mcp.json in your project, same shape as the Claude Desktop config above.
git clone https://github.com/get-mcp-ads/google-analytics-mcp-server.git
cd google-analytics-mcp-server
npm install && npm run build
cp .env.example .env # then fill in your credentials
npm start
Check your setup at any time:
npm run doctor
Every tool is listed below. See server-card.json for complete parameter and output schemas.
analyticsdata.googleapis.com,
analyticsadmin.googleapis.com and oauth2.googleapis.com. A test fails the build if a
fourth host appears in the source.redirect: "error", so a redirect
cannot forward a bearer token or client secret to another host. A test fails the build if
any fetch omits this.Full policy, including how personal data is handled: SECURITY.md.
Try hosted GA4 if you want to use this source without operating a local server. getmcpads also connects advertising, Search Console and GA4 through one MCP URL. Source availability and plan limits are listed on the site; connecting an account is still required.
See the current hosted tool catalogue and pricing before choosing a paid plan. This Apache 2.0 adapter remains independently useful with your own credentials.
Issues and pull requests are welcome. See CONTRIBUTING.md. Please read SECURITY.md before reporting anything security-related.
Apache License 2.0. See also NOTICE.
Google, Google Analytics and GA4 are trademarks of Google LLC. This project is not affiliated with, endorsed by, or sponsored by Google LLC. It is an independent client of a public API.
Every tool declares read/write annotations, parameter descriptions and a structured output schema. Successful calls expose the payload as structuredContent.result; errors retain isError: true. The generated server card contains definitions only.
Run npm run bundle -- /path/to/output to build a .mcpb desktop bundle from the current catalog. Credentials are entered locally during installation. This server remains read-only.
Maintained by Emmanuel at getmcpads. Questions: [email protected].
Google Analytics 4 MCP server: 27 read tools, no write tools.
{ "mcpServers": { "com.getmcpads-google-analytics": { "command": "npx", "args": [ "-y", "@getmcpads/[email protected]" ], "env": { "GA4_CLIENT_ID": "<value>", "GA4_CLIENT_SECRET": "<secret>", "GA4_REFRESH_TOKEN": "<secret>", "GA4_PROPERTY_ID": "<value>", "GA4_PROPERTY_IDS": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: GA4_CLIENT_ID, GA4_CLIENT_SECRET, GA4_REFRESH_TOKEN, GA4_PROPERTY_ID, GA4_PROPERTY_IDS
Google Analytics 4 ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-15 Google Analytics 4 MCP server: 27 read tools, no write tools.