← Tool directory
TOOL PROFILE

Google Analytics MCP Server

Query Google Analytics 4 with an MCP client and compare organic landing-page results against a GA4 report.

Open source

Community support

Upvotes come from SearchEngineAnswer members. GitHub stars and reader reviews are counted separately.

Claim this tool if you maintain it.

Best for
MCP servers
Setup required
Use Python 3.10 or later, pipx, an MCP client and a Google Cloud project with the Google Analytics Admin and Data APIs enabled. Use credentials with access to the intended GA4 property.
Costs to check
Apache-2.0 server. GA4 Data API quotas apply. Hosting or model usage can have separate costs.
License in catalog
Apache-2.0

GitHub repository

GitHub stars
3,841
Forks
797
Last push
2026-11-16
Primary language
Python

GitHub snapshot from . Stars count GitHub bookmarks. Reader ratings appear separately below.

How to install Google Analytics MCP Server

  1. Enable the Google Analytics Admin and Data APIs in your Google Cloud project. Follow the repository's Application Default Credentials setup and use the analytics.readonly scope for this exercise.
  2. Install pipx and register analytics-mcp with your MCP client. In the example configuration replace the credentials path and project ID locally, and keep the default read-only mode.
  3. Restart the MCP client and confirm it lists the property you intend to report on. Use the numeric GA4 property ID, rather than the web stream measurement ID.

First tutorial for Google Analytics MCP Server

  1. Choose a complete seven-day period in the property's reporting time zone. Request sessions by landingPagePlusQueryString with the sessionDefaultChannelGroup filter set to Organic Search.
    {
      "mcpServers": {
        "analytics-mcp": {
          "command": "pipx",
          "args": ["run", "analytics-mcp"],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "PATH_TO_CREDENTIALS_JSON",
            "GOOGLE_CLOUD_PROJECT": "YOUR_PROJECT_ID"
          }
        }
      }
    }
  2. Ask the client to print the property ID, date range, applied dimensions and filter beside the resulting rows. Select one well-trafficked landing page and compare its session count in a matching GA4 exploration.
  3. Repeat the report for the previous complete week. Log any filter changes separately and retain the original export so later comparisons can be reproduced.

Google's GitHub release 1.1.0 is dated November 6, 2026. Setup was checked against upstream documentation on November 21. The reporting exercise is a proposed test with an authorized property.

Official installation and usage documentation ↗

Where Google Analytics MCP Server fits

Use the server to repeat a small GA4 reporting request with explicit dates, dimensions and filters. It is useful when an SEO team wants to compare the same landing pages across complete weeks.

When to choose another tool
Use Search Console for organic Google query impressions and search clicks. Use a saved GA4 report when the team needs a shared baseline or exact control over how a report is interpreted.
First evaluation
Select one authorized GA4 property and two complete weeks. Request sessions by landing page with the Organic Search session channel group and include the reporting time zone.
How to interpret the result
Check one landing page and the matching total in GA4 with the same dates and scope. API sampling, thresholding, aggregation or a mismatched filter can explain differences. Sessions measure visits recorded by Analytics.

Reviews and discussion

Reader reviews

Be the first to share your experience with this tool.

Discussion

Ask a question or share a setup tip.

Write a review or join the discussion

Reviews should describe your own experience. All submissions are moderated.

Flag an outdated detail

Include the field that needs updating and a source link. Copy your draft, then use the corrections policy to contact the editorial team.