Data · Local MCP server

SEO Tools: Google Analytics 4

Google Analytics 4: reports, traffic sources, landing pages, events, realtime (read-only).

Visit SEO Tools: Google Analytics 4's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.antohins/seo-tools-mcp-ga4
Version
1.8.0
Status
Active
Category
data
Transport
stdio (local process)
Package
npm
Published
2026-08-25
Updated
2026-08-25
Publisher
antohins (GitHub) · 5 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/antohins) · how
Website
github.com/antohins/seo-tools-mcp#readme
Repository
github.com/antohins/seo-tools-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npmseo-tools-mcp-ga41.8.0stdioGOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), GA4_REFRESH_TOKEN (secret), GA4_SA_JSON, GA4_PROPERTY_ID, GA4_OAUTH_PORT

How to connect SEO Tools: Google Analytics 4

SEO Tools: Google Analytics 4 runs locally from a Node.js package published to the npm registry: seo-tools-mcp-ga4 version 1.8.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y seo-tools-mcp-ga4@1.8.0. It reads these environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), GA4_REFRESH_TOKEN (secret), GA4_SA_JSON, GA4_PROPERTY_ID and GA4_OAUTH_PORT; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "seo-tools-mcp-ga4": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-ga4@1.8.0"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<value>",
        "GOOGLE_CLIENT_SECRET": "<secret>",
        "GA4_REFRESH_TOKEN": "<secret>",
        "GA4_SA_JSON": "<value>",
        "GA4_PROPERTY_ID": "<value>",
        "GA4_OAUTH_PORT": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from antohins (GitHub)

All 5 →
ServerRunsEndpoint or package
SEO Tools: A-Parser bridgeBridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only).Local · stdionpm: seo-tools-mcp-aparser
SEO Tools: Google Search ConsoleGoogle Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).Local · stdionpm: seo-tools-mcp-gsc
SEO Tools: XMLRiver SERP (Google + Yandex)Google & Yandex SERP, image/news verticals and URL indexation checks via XMLRiver (read-only).Local · stdionpm: seo-tools-mcp-xmlriver
SEO Tools: Yandex WordstatMCP server for Yandex Wordstat keyword frequencies (official API v2). Free Yandex Cloud Search API.Local · stdionpm: seo-tools-mcp-wordstat

More data servers

All 4,815 →
ServerRunsEndpoint or package
Seo SerpSEO SERP MCP - Google organic search results via DataForSEO (dataforseo.com)Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
Seo Stack MCPThe complete open-source SEO data stack for AI agents: 7 sources, 86 tools, one MCP server.Local · stdioPyPI: seo-stack-mcp
Seo ToolsSEO tools via x402: briefs, keywords, SERP, backlinks, audits. $0.50-$3/req USDC on Base.Local · stdionpm: @seodesignlab/mcp-server
SEO Trends APISpot keyword demand rising or fading across search and social. Free key at trendsapi.ai.Remote · HTTPLive check: ✓ handshakeseo.api.trendsapi.ai
SEO Trends MCPSpot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai.Remote · HTTPLive check: ✓ handshakeseo.api.trendsmcp.ai
Seo Web Analysis MCP ServerSite crawl + tech stack + DNS + SSL + WHOIS - five web-intel layers in one MCP.Remote · HTTPLive check: sign-in requirednexgendata-mcp-proxy.steve-corbeil.workers.dev