Google Analytics in Claude Code
Add Caybl.ai to Claude Code as a remote MCP server and your GA4 data is available from the terminal. One command, one browser authorization, then ask.
- Free to connect and read
- Read-only by default
- One command to add
Can Claude Code read Google Analytics?
Yes. Claude Code connects to remote MCP servers, which is the same mechanism the Claude desktop and web apps use for custom connectors. Because Caybl.ai is hosted, one connection covers all three - you authorize once and the same GA4 access is there whether you are in the terminal or the browser.
Steps
Sign in with Google
Connect Google Analytics through Google’s own consent screen.
Copy your endpoint
From your Caybl.ai dashboard.
Add it to Claude Code
claude mcp add for the remote HTTP transport - it opens the browser to authorize.
Ask
“Did organic traffic to the docs drop after last Tuesday’s deploy?”
Add it at user scope to have it in every project, or project scope to keep it to the one repository. Project scope is usually right when a repo maps to a specific website.
Skill, plugin, connector, or MCP server?
These names get used interchangeably and it is a fair source of confusion. For live data from an outside service, the mechanism Claude actually uses is MCP. A connector is what the Claude apps call an MCP server you have added. Skills and plugins package instructions and behaviour rather than a live connection to your account. Caybl.ai is an MCP server, which is why a single connection works across Claude Code, desktop and web.
Why this beats a local Google Analytics MCP server
The self-hosted route is free and genuinely works, but it asks you to create a Google Cloud project, enable the Data API, generate credentials, grant your service account access to the GA4 property, and keep a local process running. The failure modes are well documented and unpleasant: credentials in the default gcloud path can deadlock the server until the call times out, and a service account missing property access returns empty results with no error at all - so it looks like you have no data rather than no permission.
Caybl.ai removes that surface entirely. There is no key file, no local process, and access is granted through the standard Google consent screen you can revoke at any time.
Questions worth asking from the terminal
- Compare“Compare traffic to the pages I changed this week against the previous week.”
- Analyze“Which routes have the highest bounce rate on mobile?”
- Diagnose“Did the redirect I shipped on Monday cost us any organic entrances?”
- Analyze“What are the top landing pages for this site, and which convert worst?”
“Did the redirect I shipped on Monday cost us any organic entrances?”
“Organic entrances to /docs/getting-started are down 18% since Monday - the redirect target is missing the old URL’s top ranking query in its title.”
Illustrative example - not real account data.
Add Google Analytics to Claude Code
Hosted, one command. No service accounts, no local server.
Get started free →FAQ
Yes. Claude Code supports remote MCP servers, and Caybl.ai is one. You add the endpoint once with claude mcp add, authorize in the browser, and Claude Code can query your GA4 property from the terminal in any project.
Skill, plugin, connector and MCP server all describe routes to the same outcome, and the one Claude actually uses for live outside data is MCP. Caybl.ai is a hosted MCP server, so it works in Claude Code, Claude desktop and the web app from a single connection - there is nothing separate to install per client.
No. That is the setup the self-hosted servers require, and it is where most of the reported problems come from - credential paths, service accounts missing GA4 property access, a local process that has to stay running. Caybl.ai is hosted and authorizes over OAuth in the browser, so none of it applies.
Add it with user scope and it is available everywhere. Add it with project scope and it stays in the one repository, which is the better choice when a project maps to a specific site.
Only in two narrow, specific ways: Caybl.ai's Analytics scope allows marking a GA4 event as a key event and linking a Google Ads account to your property, if you ask for either. There's no path to change property settings, audiences, or your website.
Sources
- Claude Code documentation - connecting remote MCP servers
- Google Analytics Data API (v1) - official Google documentation
- Model Context Protocol (MCP) - the open standard for connecting AI clients to data