Read-only Google Analytics 4 MCP server with local OAuth and multi-account support.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"flin-ga4-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# flin-ga4-mcp Read-only Google Analytics 4 MCP server for Claude Desktop and other stdio MCP clients. Built on the same Python/FastMCP architecture as flin's Search Console and Keyword Planner servers: local browser OAuth, per-account token files, `uv`, and GitHub/PyPI releases. ## Quickstart 1. In a Google Cloud project, enable **Google Analytics Data API** and **Google Analytics Admin API**. 2. Configure the OAuth consent screen. If the app is External/Testing, add your Google account as a test user. Testing authorizations can expire after seven days. 3. Create an OAuth client of type **Desktop app** and copy its client ID and client secret. 4. Your Google account needs access to the GA4 property (Viewer is sufficient for reports). 5. Clone this repository and add the following to your MCP client's configuration: ```json { "mcpServers": { "flin-ga4-mcp": { "command": "uv", "args": ["run", "--directory", "/absolute/path/to/flin-ga4-mcp", "--locked", "--no-dev", "flin-ga4-mcp"], "env": { "GOOGLE_CLIENT_ID": "your-desktop-oauth-client-id", "GOOGLE_CLIENT_SECRET": "your-desktop-oauth-client-secret", "GOOGLE_GA4_PROPERTY_ID": "123456789" } } } } ``` Replace the path and credentials. The default property ID is optional. Use the numeric **property ID**, not a `G-...` measurement ID or a Google Analytics account ID. Restart your MCP client after changing its configuration. Ask the assistant to run `health_check`, then `list_properties`. The first data request opens Google sign-in in your browser. Complete it within three minutes. Subsequent calls reuse/refresh the saved token. `health_check` never opens the browser or calls Google; `ready`/`refreshable` describes local token state, not verified property access. Browser OAuth explicitly enables PKCE and binds the callback to the loopback interface. Only `https://www.googleapis.com/auth/analytics.readonly` is requested. No analytics settings, events, au…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.