How to Connect Google Analytics to Claude with the GA MCP Server

Checking Google Analytics usually means logging in, choosing a report, setting a date range, and clicking through menus to find one number. It works, but it is slow when all you want is a quick answer.

There is now a faster way. Google publishes an official Google Analytics MCP server that connects your GA4 data to an AI assistant like Claude. Once it is set up, you ask a question in plain language and get the answer back in seconds.

This guide walks through the full install on a Mac, from the command line tools to the Google Cloud setup, and ends with the exact prompts you can start using. No prior experience with MCP is needed.

Skip to the install steps

What Is an MCP Server?

MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant connect to outside tools and data sources, so the model can do more than talk.

The Model Context Protocol was introduced by Anthropic in late 2024, and many AI apps support it today. If the idea is new to you, our guide on how to connect MCP servers to Claude Code covers the basics.

“Think of MCP like a USB-C port for AI applications.” – Model Context Protocol documentation

A single MCP server exposes one system as a set of tools. The Google Analytics MCP server exposes your GA4 reporting data, so Claude can pull metrics, run reports, and read property details on your behalf.

It is an official Google project, published on GitHub as the analytics-mcp package. That is the one this guide installs. Google still labels it experimental, and new versions ship often, so I cover how to update it below.

What You’ll Need Before You Start

The setup has a few moving parts, but each one is quick. Here is what to have ready before you begin.

• Claude Code. The install below registers the server with Claude Code, Anthropic’s command line assistant. The same analytics-mcp package also works with Cursor and the Gemini CLI, with a slightly different config step.
• A Google account with GA4 access. You need access to at least one Google Analytics 4 property. If you have not set one up yet, start with our guide on how to add Google Analytics 4 to WordPress.
• A Google Cloud project. This is free to create. It is where you enable the Analytics APIs and create login credentials.
• Homebrew on macOS. The commands here use Homebrew to install two tools. Windows and Linux use the same packages through their own installers.
• About 15 minutes. Most of that is the one-time Google Cloud setup.

How to Install the Google Analytics MCP Server

The process has eight steps. The first three install command line tools, the next three set up Google Cloud access, and the last two register the server and confirm it works.

Step 1: Install pipx

pipx installs and runs Python command line apps in their own isolated environments. The analytics-mcp server is a Python app, so pipx is the cleanest way to run it.

Install it with Homebrew.

brew install pipx
pipx ensurepath

One nice detail here: pipx pulls in its own recent version of Python. Your system Python can be old, and it does not matter, because the server runs inside the environment pipx manages.

Step 2: Install the analytics-mcp Package

With pipx ready, install the Google Analytics MCP server itself. This downloads the package and creates a command you can point Claude Code at.

pipx install analytics-mcp

When it finishes, pipx reports the installed version and adds an analytics-mcp command to your ~/.local/bin folder. You will use that path in Step 7.

The package gets regular releases. To move to the latest version later, run pipx upgrade analytics-mcp and restart Claude Code.

Step 3: Install the Google Cloud SDK

The server signs in to Google using credentials created by the gcloud command line tool. Install the Google Cloud SDK, which provides it.

brew install --cask google-cloud-sdk

This is the largest download in the guide. Once it is done, the gcloud command is available in your terminal.

Step 4: Create a Project and Enable the APIs

Now switch to your browser. Open the Google Cloud Console, then create a new project or pick an existing one. Note the project ID, since you will need it later.

Next, enable the two APIs the server relies on. In the console, search for each one and click Enable.

• Google Analytics Admin API. This lets the server list your accounts and properties.
• Google Analytics Data API. This is what runs the actual reports, such as users and sessions.

If you skip either API, the server still connects, but the matching requests fail later. Enable both now to avoid confusion.

Step 5: Create OAuth Credentials

The server needs permission to read your Analytics data on your behalf. You grant it through an OAuth client, which you create in the same project.

First, open the Google Auth Platform section and set up the consent screen. Choose External as the user type, add an app name and your email, and save.

Then add yourself as a test user. This step is easy to miss, and it is the most common cause of a failed login.

Now create the client itself. Go to the Clients section, click Create client, choose Desktop app as the type, give it a name, and click Create. Then download the JSON file and save it somewhere stable, such as your gcloud config folder.

Step 6: Sign In With gcloud

Back in the terminal, run the login command below. It points gcloud at the client file you just downloaded and asks for read only access to Analytics.

gcloud auth application-default login \
  --scopes=https://www.googleapis.com/auth/analytics.readonly,https://www.googleapis.com/auth/cloud-platform \
  --client-id-file=YOUR_CLIENT_FILE.json

Your browser opens a Google consent screen. Sign in, approve the request to see your Analytics data, and wait for the page to confirm that authentication is complete.

You may see a warning that Google has not verified the app. That is expected for a personal client. Click Advanced, then continue to your app to proceed.

When it finishes, gcloud saves your credentials to a file it calls the Application Default Credentials. The path is printed in the terminal. Copy it, because the next step uses it.

Each run of this command replaces the saved credentials file. If other tools on your machine use the same Application Default Credentials, for example a Search Console script, add their scopes to the --scopes list every time, or those tools lose access.

Step 7: Register the Server in Claude Code

You now have everything the server needs: the installed command, your project ID, and your saved credentials. Register it with a single claude mcp add command.

claude mcp add analytics-mcp --scope user \
  -e GOOGLE_APPLICATION_CREDENTIALS=/path/to/application_default_credentials.json \
  -e GOOGLE_CLOUD_PROJECT=your-project-id \
  -- /Users/you/.local/bin/analytics-mcp

Two environment values do the work here. GOOGLE_APPLICATION_CREDENTIALS points to the credentials file from Step 6, and GOOGLE_CLOUD_PROJECT is the project ID from Step 4. Use that exact name: it is the variable Google’s auth library reads, and an earlier version of this guide used GOOGLE_PROJECT_ID, which is ignored.

Using the full path to the analytics-mcp command, rather than a short name, keeps Claude Code from depending on your shell setup when it launches the server.

Step 8: Verify the Connection

Confirm the server is registered and healthy with the list command.

claude mcp list

You want to see analytics-mcp reported as connected, like this.

analytics-mcp: /Users/you/.local/bin/analytics-mcp - Connected

Using the Claude Desktop App Instead

Prefer the Claude desktop app to Claude Code? It runs the same local server. You keep Steps 1 to 6 as they are and replace Step 7 with an entry in the app’s config file.

The file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. You can also open it from Settings, then Developer, then Edit Config. Add the server under mcpServers:

{
  "mcpServers": {
    "analytics-mcp": {
      "command": "/Users/you/.local/bin/analytics-mcp",
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "/path/to/application_default_credentials.json",
        "GOOGLE_CLOUD_PROJECT": "your-project-id"
      }
    }
  }
}

Use the same values as in Step 7. Then quit Claude Desktop completely and open it again, since it only loads new servers on startup. The steps come from the official MCP guide to local servers.

What You Can Ask Claude Once It Is Connected

The server adds nine read only tools to Claude. You never call them by name. You ask a question, and Claude picks the right tool and fills in the details.

Version 0.8.0 (October 2026) added one optional write tool, create_property_annotation, which adds a note to a property for a date, such as a release or a campaign launch. It is off by default. To turn it on, append --allow-write to the server command and sign in again with the analytics.edit scope added to the scopes list. Your account also needs at least the Marketer role on the property.

Here are prompts that map to those tools. Try them once the server is connected.

• “Which Google Analytics properties can I access?” lists your accounts and properties.
• “How many people are on my site right now, and what pages are they viewing?” runs a realtime report.
• “Show me users and sessions for the last 28 days, split by channel.” runs a standard report.
• “What were my top 10 landing pages last month by users?” runs a standard report with a sort and a limit.
• “Where do visitors drop off between viewing a product and starting checkout?” builds a funnel report.

Because Claude reads the data live, you can keep the conversation going. Ask it to compare two date ranges, explain a spike, or focus on one country, all without touching the dashboard.

This pairs well with tracking where that traffic comes from. If you are watching the rise of AI referrals, see our guide on how to track AI traffic in Google Analytics 4.

Troubleshooting Common Setup Problems

Most setup issues come from one of a few places. Here is how to clear the ones you are most likely to hit.

• access_denied 403 during sign in. Your account is not a test user on the OAuth consent screen. Add it under the Audience or Test users section, then run the login again.
• The Analytics tools do not appear in Claude. The server was added mid session. Restart Claude Code or open a new session so the tools load.
• A request fails with an API not enabled error. One of the two APIs from Step 4 is off. Enable both the Analytics Admin API and the Analytics Data API.
• invalid_grant error after it worked before. Your refresh token expired, which happens every 7 days while the OAuth app is in Testing mode. Run the gcloud auth application-default login command from Step 6 again.
• Claude cannot start the server. Check the command path in your claude mcp add line. Using the full path to analytics-mcp avoids problems with your shell PATH.

If a report returns no rows, confirm the property has data for the date range you asked about, and that your account can see that property in the Analytics interface.

FAQs

Common questions about the Google Analytics MCP server:

Summary

The Google Analytics MCP server turns GA4 reporting into a conversation. Instead of clicking through the dashboard, you ask Claude and get the number back right away.

The setup is a one time job. Install pipx, the analytics-mcp package, and the Google Cloud SDK, then enable the two Analytics APIs, create an OAuth client, and sign in. Register it with claude mcp add and confirm it connects.

From there, your Analytics data is one question away. Ask for realtime visitors, traffic by channel, or your top landing pages, and let Claude do the clicking for you.