Google Analytics
LiveGA4 traffic, pages and sources, asked in plain language.
Connect the same Google account you use for Search Console Insights, then ask for sessions, top pages, channels and a property list. Read-only: nothing is changed in Google Analytics.
Server URL
https://toolcargo.com/mcp/google-analyticsClaude Code
claude mcp add --transport http --scope user toolcargo-google-analytics https://toolcargo.com/mcp/google-analytics \
--header "Authorization: Bearer YOUR_API_KEY"Create a key in your dashboard. Other clients: setup guides.
What it helps you do
- Sessions, users and views for a period
- Top pages by views
- Traffic grouped by channel and source
Built for: Marketers and agencies who already have GA4 on client sites.
Example requests
Weekly traffic
“With ToolCargo, traffic overview for GA4 property 123456789 over the last 28 days.”
Sessions, active users, views and engagement rate.
What pages work
“Top pages for that property last 28 days.”
Paths ranked by views, with sessions and users.
Where traffic comes from
“Traffic sources for that property.”
Channel and source with sessions.
Step-by-step workflows: pre-launch check · fixing link previews
Tools
| Tool | What it does | Access |
|---|---|---|
list_propertiesList GA4 properties | The Google Analytics 4 properties this connected Google account can read. | Read-only |
traffic_overviewTraffic overview | Sessions, active users, views and engagement rate for a GA4 property over a period ending yesterday. | Read-only |
top_pagesTop pages | The pages with the most views in the period, with sessions and users. | Read-only |
traffic_sourcesTraffic sources | Sessions and users grouped by default channel and source. | Read-only |
Requirements
- • A Google account with access to a GA4 property.
- • Connect Google Analytics once (read-only) on the Google Analytics page. Search Console uses the same Google account.
- • While Google reviews the app, only invited test accounts can connect.
Limitations
- • Read-only: nothing is changed in Google Analytics.
- • Periods end yesterday. Totals cover the rows Google returns.
- • Needs the analytics.readonly scope on ToolCargo's Google OAuth client. If connect fails on scope, the consent screen still needs that scope added.
Supported clients
“Tested” means we connected that client to this endpoint and ran a tool call ourselves. “Documented” means the client supports this setup per its own docs, but we have not tested it yet.
| Claude Code | API key header | Tested | Remote HTTP server with an Authorization header. Tested 2026-09-11 (v2.1.268). |
| Claude (claude.ai) | OAuth sign-in | Tested | Custom connector with OAuth sign-in; tested on claude.ai web 2026-09-11. Desktop and mobile use the same account connectors but were not tested separately. |
| Cursor | API key header | Documented, not yet tested | mcp.json with url and headers. |
| VS Code (Copilot agent mode) | API key header | Documented, not yet tested | .vscode/mcp.json with type http and headers. |
| ChatGPT (developer mode) | OAuth sign-in | Documented, not yet tested | Requires OAuth; API keys cannot be entered. |
| MCP Inspector | API key header | Tested | CLI mode, tested 2026-09-11. Useful for calling tools directly. |
More in Analytics
Pricing
Free
$0For trying the connector on your own sites.
50 calls/month · 25 links per check
Pro
$12/moFor freelancers and agencies auditing client sites every week.
2,000 calls/month · 100 links per check
Proposed test price. See the pricing page for checkout status.