Agents and MCP

Google Analytics in Claude, without a Cloud project.

Add the LopeBase connector to Claude and connect GA4 with Google. Claude can then read traffic, channels, landing pages, devices, and goal conversions for each of your properties, and think through what the numbers mean for you.

Works in Claude on the web, the desktop app, and Claude Code. Read only.

What it looks like in Claude

One question, one tool call, and an answer built on your own GA4 numbers.

Claude · LopeBase connector

Where do our best signups come from, and what should I do about it?

read_sourcega4-acmetraffic_sourcesgoal: sign_up

channelvisitorssessionssignups
Organic Search9,42012,871212
Referral1,3771,70261
Paid Search2,0602,41022
Organic Social2,9153,24017

Search brings the most signups, but Referral converts at about 4.4%, twice your average, from a small base. Paid search converts at about 1%. I would move some ad budget into getting listed on the sites that already refer you.

Claude gets the outcome, not just traffic

Pass a goal and every breakdown counts conversions, so Claude can rank by what matters.

Mix it with your own context

In a Claude project with your pricing or roadmap, Claude can tie GA4 numbers back to your plans.

Listed in Claude's directory

Add LopeBase from the directory with a couple of clicks. No address to copy, no config file.

Add LopeBase to Claude

Three steps. The first is the same for every app; the rest is specific to Claude.

  1. 01

    Connect GA4 to LopeBase. Start free, add your site, press Connect with Google, and pick the GA4 property. You need no Google Cloud project and no API key. Google is only asked for read access.

  2. 02

    Add the LopeBase connector. LopeBase is listed in Claude's connector directory: open it there and press Connect. Or, in Claude's settings under Connectors, add a custom connector with the address https://app.lopebase.com/api/mcp.

  3. 03

    Approve it and ask. Claude opens a LopeBase page. Approve it for your workspace and the connector works in Claude on the web and in the desktop app, in any chat or project.

Find LopeBase in the Claude directory

Working in a terminal? Add the same server to Claude Code:

$ claude mcp add --transport http lopebase https://app.lopebase.com/api/mcp

Custom connectors depend on your Claude plan; the directory listing is the quickest route. Claude Code signs in the same way the first time it calls a LopeBase tool.

GA4 prompts that work well in Claude

Claude handles nuance well. Ask it questions with a decision attached.

Write the monthly report

Write a one page traffic report for all my products, with what to do next.

Headline numbers, then the why from channels and pages.

web_analyticstraffic_sourcesget_digest

Judge a channel by signups

Rank channels by conversion to sign_up and explain any surprises.

Turns a traffic report into an outcome report.

traffic_sourcesgoal_events

Pair search with sessions

For our top Search Console pages, how do those visitors behave once they land?

With Search Console connected too, Claude joins the two by page.

top_pageslanding_pages

Review a landing page

Which landing pages get over 500 visitors and bounce above 70%? Suggest one fix each.

Claude can read the live page and point at the cause.

landing_pages

What Claude can read from GA4

Seven datasets per GA4 property. Breakdowns cover the last 28 days and the trend up to 90. Pass any event as a goal to count conversions.

  • web_analyticsPageviews for 7 and 28 days, plus weekly and monthly users.pageviews_7d · pageviews_28d · wau · mau
  • daily_pageviewsPageviews and visitors per day.day · pageviews · visitors
  • top_pathsThe most viewed pages over the last 7 days.url · views · visitors
  • goal_eventsEvents that may count as a conversion, now and before.event · people_28d · people_prev_28d · people_7d
  • traffic_sourcesVisitors and sessions per channel. Add a goal for conversions.source · visitors · sessions · converters
  • landing_pagesVisitors and bounce rate per landing page.path · visitors · converters · bounce_rate
  • devicesVisitors per device. Add a goal for conversions.device · visitors · converters

More on each dataset: Google Analytics MCP. Connecting in the console: the GA4 connector.

Other ways to get GA4 into Claude

LopeBase is not the only route. Here is how it compares with the usual one.

TopicGoogle's Analytics MCP serverLopeBase
SetupPython and pipx, a Google Cloud project with two Analytics APIs turned on, and local credentials.Connect with Google, then add LopeBase from Claude's directory.
Where it runsOn your computer, for local clients like Claude Desktop.Claude on the web, the desktop app, and Claude Code.
FlexibilityRuns any GA4 report you describe, including custom dimensions.Seven shaped datasets, built for the common questions.
Other dataGA4 only.Search Console, Bing, PostHog, Stripe, and uptime alongside it.
Best whenYou are comfortable in Google Cloud and need custom reports.You want GA4 in Claude in minutes, alongside your other data.

Google's server is described from its own README, checked October 2026. It is labeled experimental there.

GA4 and Claude questions

Something else? Contact us.

Is LopeBase in Claude's connector directory?

Yes. Search for LopeBase in the directory and press Connect. Or add a custom connector with the address https://app.lopebase.com/api/mcp.

Do I need a Google Cloud project for GA4?

No. Connect with Google handles access, and LopeBase calls the GA4 Data API for you.

Will Claude's numbers match the GA4 interface?

They come from the same Data API. Small differences can come from GA4's own thresholds, the same as you see in explorations.

Can Claude see individual users?

No. Claude gets counts and rates per channel, page, and device. Never a visitor, an IP address, or a user ID.

Can I use it in Claude Code?

Yes. Run claude mcp add --transport http lopebase https://app.lopebase.com/api/mcp, or npx lopebase in the project folder.

Let Claude read GA4 for you.

Free for one product. No card. Agent access is on every plan.