Bring Web Analytics
to Claude Desktop
Learn how to connect Google Analytics 4 to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Google Analytics 4 MCP Server?
Connect your Google Analytics 4 property to any AI agent and access web analytics through natural conversation.
What you can do
- Custom Reports — Run fully customizable GA4 reports with any combination of dimensions, metrics, and date ranges
- Real-Time Analytics — Monitor active users and current page views in real time
- Page Performance — Retrieve the top 25 pages ranked by views for any time period
- Traffic Sources — Analyze session sources and mediums to understand where visitors come from
- User Demographics — View user distribution by country for geographic insights
- Device Breakdown — See user distribution across desktop, mobile, and tablet
- Conversions — Track conversion events with counts and revenue data
- Advanced Reporting — Run pivot reports and batch multiple reports in a single request
- Metadata & Compatibility — List all available dimensions and metrics, and verify compatibility before building reports
How it works
1. Subscribe to this server
2. Enter your Google OAuth Access Token and GA4 Property ID
3. Start querying your analytics from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Marketing Teams — track campaign performance, traffic sources, and conversion funnels without opening the GA4 dashboard
- Product Managers — monitor feature adoption through page views and user engagement metrics
- Growth Engineers — analyze device breakdown, demographics, and real-time traffic patterns to optimize user experience
Built-in capabilities (12)
Batch run reports
Check report compatibility
Get conversions
Get device breakdown
Get available dimensions and metrics
Get top pages by views
Get traffic sources
Get user demographics
List audience exports
Run pivot report
Run realtime report
Data JSON must include dateRanges, dimensions, and metrics arrays. Run a custom report
Why Claude Desktop?
Claude Desktop is the definitive way to connect Google Analytics 4 to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Google Analytics 4 in Claude Desktop
Google Analytics 4 and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Google Analytics 4 to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Google Analytics 4 in Claude Desktop
The Google Analytics 4 MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Google Analytics 4 for Claude Desktop
Every tool call from Claude Desktop to the Google Analytics 4 MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I run custom reports with specific dimensions and metrics?
Yes! The run_report tool accepts a JSON configuration with dateRanges, dimensions (e.g., pagePath, sessionSource), and metrics (e.g., sessions, screenPageViews, conversions). Use get_metadata to list all available dimensions and metrics, and check_compatibility to verify your combination is valid before running.
Does GA4 require two credentials — an access token and a property ID?
Yes. You need a Google OAuth Access Token (for authentication via Bearer header) and a GA4 Property ID (numeric ID identifying your specific GA4 property). The Access Token can be generated via a Google Cloud Service Account with the Analytics Data API enabled. The Property ID is found in GA4 Admin > Property Settings.
Can I see real-time active users on my website?
Yes. The run_realtime_report tool provides current active user data with real-time dimensions and metrics. For pre-built convenience reports, use get_page_views for top pages, get_traffic_sources for session sources, and get_device_breakdown for device distribution.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.