How to Connect Google Analytics to Claude?

Before you start

You'll need a SourcetoMCP account with at least one brand created, a Google account with access to at least one GA4 property, and a Claude account. Custom connectors work on Free, Pro, Max, Team and Enterprise, though Free accounts are limited to one at a time.

Viewer access on the property is enough to read reports. Editor or Administrator access is required for the operations that change property settings, which are covered further down.

Connect Google Analytics to SourcetoMCP

1. 1From your dashboard, go to Connectors → Add a connection.
2. 2Find the Google Analytics card and select Connect.
3. 3Sign in with the Google account that has access to the property you want. This opens Google's own consent screen on accounts.google.com. Read what it asks for: SourcetoMCP requests access to your Analytics data and to your property configuration, because the connector can create custom dimensions, audiences and annotations as well as read reports.
4. 4Back in SourcetoMCP, pick which GA4 propert(ies) to connect. Each one is listed as account name, property name and property id, so two properties with the same name stay easy to tell apart. Confirm, and each connected property shows up on your Connections page.

SourcetoMCP never sees your Google password. The connection is an OAuth grant you can withdraw from your Google account at any time.

Add SourcetoMCP as a connector in Claude

1. 1In SourcetoMCP, open Connect an agent from the dashboard sidebar and copy your server address (it looks like https://sourcetomcp.com/api/mcp).
2. 2In Claude, open Customize, then Connectors.
3. 3Select +, then Add custom connector.
4. 4Paste in your server address. You can leave Advanced settings alone, because SourcetoMCP runs its own OAuth and never needs a client ID or secret from you.
5. 5Click Add.
6. 6The first time Claude uses it, you'll be asked to sign in to SourcetoMCP and approve access, the same OAuth approval you'd see connecting any other app. After that it reconnects on its own.

On a Team or Enterprise plan, only an Owner can add a connector, from Organization settings, then Connectors. Everyone else then opens Customize → Connectors and clicks Connect to sign in with their own SourcetoMCP account, so each person only ever reaches the sources their own account can see.

Once approved, the connection appears under Active connections on the Connect an agent page in SourcetoMCP, so you can see exactly what has access at any time.

Ask Claude about your GA4 property

Adding the connector makes it available, and you still switch it on per conversation. In a chat, select the + button, choose Connectors, and toggle SourcetoMCP on.

Claude shows a panel for each tool call, named in plain English, so you can see which data it pulled and check the numbers came from your property rather than from the model.

With both pieces connected, Claude reaches four kinds of report from the same property: traffic and engagement, conversions and e-commerce, audience and demographics, and real-time activity. Try something like:

1. 1What were our top traffic channels last month by sessions?
2. 2Compare purchase revenue for the last 28 days against the previous 28 days.
3. 3Which landing pages have the highest engagement rate this quarter?
4. 4How many active users are on the site right now?

Two limits are worth knowing before you read the numbers. GA4 keeps refining recent data for 24 to 48 hours, so today and yesterday can move after you ask. Real-time covers roughly the last 30 minutes, which is a different question from a report about today.

Age and gender rows only come back when Google Signals is turned on for the property, and Google withholds rows that fall below its own minimum-traffic thresholds. Empty demographic rows usually mean one of those two things rather than a broken connection.

What Claude can change in GA4

The Google Analytics connector is not read-only, which sets it apart from most sources in SourcetoMCP. Alongside the reports, Claude can create custom dimensions and metrics, mark conversion events, build a simple event-triggered audience, add a web data stream, create a property, update the time zone, currency, data retention and Google Signals settings, link or unlink a Google Ads account, and add reporting annotations.

Claude asks you to approve each write before it runs, and the approval names the operation and the property it applies to. Read that prompt rather than clicking through it, because some of these changes are awkward to undo: archiving a custom dimension loses its collected data, and GA4 caps how many custom dimensions a property can have.

Starting a brand new GA4 account is the one operation Claude cannot finish on its own. It can begin provisioning, and a person still has to accept Google's Terms of Service to complete it.

Troubleshooting

My property isn't in the list when connecting: the signed-in Google account has no access to that GA4 property. Add the account in Google Analytics under Admin → Property access management, then reconnect. A Google account can also hold access to several Analytics accounts, so check you signed in with the right one.

There is no Connectors option under Customize: on Team and Enterprise plans an Owner adds connectors for the whole organisation. Ask an Owner to add it from Organization settings → Connectors, and it will then show up for you to connect.

Claude won't let you add another connector: Free accounts can keep one custom connector at a time. Remove the one you have, or move to Pro or Max.

Numbers don't match the GA4 interface: check the date range and the property id in Claude's tool-call panel first, then check whether the range includes the last 48 hours, where GA4 is still processing. A report run against a different property is the most common cause when the gap is large.

Claude says it can't find the tool or has no data: check SourcetoMCP is toggled on for that conversation under the + menu. If it is, confirm the connection still shows under Active connections in SourcetoMCP, then remove and re-add it to trigger a fresh approval.

Revoking access

You can disconnect from either side. In SourcetoMCP, remove the property from your Connections page, or revoke Claude's access entirely from the Connect an agent page. In Claude, open Customize → Connectors and remove it. On Team and Enterprise an Owner removes it for everyone from Organization settings → Connectors. To cut the Google side as well, remove SourcetoMCP from your Google account's third-party access list.

Still stuck?

Reach us at [email protected].