Google Analytics

Google Analytics

Official

Query GA4 reports, funnels, and realtime data from an AI agent.

Score 86(?)Google AnalyticsApache-2.02.4kVerified Top MCPs for Marketing & SEO

Quick answer

What it does

Connects to GA4 via the Analytics Data API and Admin API and exposes account/property summaries, run_report, run_funnel_report, run_realtime_report, and custom dimension/metric metadata as MCP tools. Read-only.

Best for

  • Ad-hoc GA4 reporting
  • Funnel and conversion analysis
  • Realtime traffic checks
  • Channel and campaign attribution queries

Not for

  • Universal Analytics data
  • Writing GA4 configuration

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "google-analytics": {
          "command": "pipx",
          "args": [
            "run",
            "analytics-mcp"
          ],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    }

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-key.json (or gcloud ADC)
    claude mcp add google-analytics -- pipx run analytics-mcp

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
      "mcpServers": {
        "google-analytics": {
          "command": "pipx",
          "args": [
            "run",
            "analytics-mcp"
          ],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
      "servers": {
        "google-analytics": {
          "command": "pipx",
          "args": [
            "run",
            "analytics-mcp"
          ],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    }

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "google-analytics": {
          "command": "pipx",
          "args": [
            "run",
            "analytics-mcp"
          ],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    }

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "google-analytics": {
          "command": "pipx",
          "args": [
            "run",
            "analytics-mcp"
          ],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    }

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "stdio",
              "command": "pipx",
              "args": [
                "run",
                "analytics-mcp"
              ],
              "env": {
                "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
              }
            }
          }
        ]
      }
    }

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
    [mcp_servers.google-analytics]
    command = "pipx"
    args = [
      "run",
      "analytics-mcp",
    ]
    env = { GOOGLE_APPLICATION_CREDENTIALS = "${GOOGLE_APPLICATION_CREDENTIALS}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "google-analytics": {
          "command": {
            "path": "pipx",
            "args": [
              "run",
              "analytics-mcp"
            ]
          },
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    }

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Google Analytics doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set GOOGLE_APPLICATION_CREDENTIALS in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

ToolDescriptionArgsSide effects
get_account_summariesList the GA4 accounts and properties the credential can access.Read
get_property_detailsReturn metadata for a GA4 property.property: stringRead
run_reportRun an ad-hoc GA4 report with dimensions and metrics.Read
run_funnel_reportRun a funnel report across ordered steps.Read
run_realtime_reportReturn realtime active-user metrics.Read
get_custom_dimensions_and_metricsEnumerate custom dimensions and metrics defined on a property.property: stringRead

Security & scope

Access scope
Read-only
Sandbox
Authenticates via Google ADC with the analytics.readonly scope. Every exposed tool is a report read against the GA4 Data or Admin API — no tool can mutate the property. Grant the service account read access only on the specific GA4 properties the agent should see.
Gotchas
  • Service-account keys in env persist in client config files. Prefer gcloud ADC + short-lived login over a long-lived key file.
  • Grant the credential on only the GA4 properties the agent needs — a single key with org-wide access over-exposes data.
  • Realtime and large date-range reports consume Data API tokens; very high-frequency agent loops can hit the quota.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. marketing & seo work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-marketing-seo
Compare Google Analytics against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Google Analytics MCP vs [Google Search Console MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/google-analytics
- top-mcps.com listing for Google Search Console
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Google Analytics MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/google-analytics (fetch https://top-mcps.com/mcp/google-analytics.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (GOOGLE_APPLICATION_CREDENTIALS) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Marketing & SEO MCPs

Other tools in the same category worth evaluating.

DataForSEO
Official

Live SERP, keyword, backlink, and on-page SEO data for an AI agent.

seo, serp, keywords, backlinks
10 minMedium
Google Search Console

Query Search Console clicks, impressions, and queries from an AI agent.

seo, search-console, gsc, organic-search
15 minMedium
Ahrefs
Official

Backlinks, keyword research, and rank tracking from the official Ahrefs remote MCP.

seo, backlinks, keywords, rank-tracking
5 minLow

Compared with Google Analytics

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Marketing & SEO? See all Marketing & SEO MCPs →