Use them when developing, testing, linting, formatting, or checking this Google Analytics MCP server.

They give a coding agent the project-specific commands and conventions needed to work safely in the repository.

How ruchernchong/mcp-server-google-analytics configures Claude Code

Q: What is mcp-server-google-analytics CLAUDE.md?

Repository instructions for building, running, testing, and checking an MCP server that provides Google Analytics 4 data access. The instructions cover its TypeScript commands, project structure, and quality tools.

Reuse

Borrowing it

Nothing to install: this file belongs to ruchernchong/mcp-server-google-analytics. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ruchernchong/mcp-server-google-analytics/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/ruchernchong/mcp-server-google-analytics

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ruchernchong/mcp-server-google-analytics/claude-md/github.svg)](https://agentmods.dev/instructions/ruchernchong/mcp-server-google-analytics/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/ruchernchong/mcp-server-google-analytics/claude-md"><img src="https://agentmods.dev/badge/instructions/ruchernchong/mcp-server-google-analytics/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ruchernchong/mcp-server-google-analytics/claude-md"><img src="https://agentmods.dev/badge/instructions/ruchernchong/mcp-server-google-analytics/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 663 This file is loaded in full into every session.

When invoked 663 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00663	$0.00663
Opus 5.5	$0.00265	$0.00265
Sonnet 5.5	$0.00133	$0.00133
Haiku 4.5	$0.00066	$0.00066

Measured 2mo ago against content hash 1ffa6118d460, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-server-google-analytics CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Essential Commands

Build and Development

pnpm build - Compile TypeScript to JavaScript (output in dist/)
pnpm dev - Run the server in development mode with ts-node
pnpm start - Start the compiled server from dist/index.js

Testing

pnpm test - Run Vitest tests from the tests/ directory
Tests are configured with Vitest and target Node.js environment

Code Quality

pnpm lint - Run Biome linter on src/ directory
pnpm format - Format code with Biome (writes changes)
pnpm check - Run Biome check and apply fixes automatically

Project Architecture

Core Structure

This is a Model Context Protocol (MCP) server that provides Google Analytics 4 data access. The architecture consists of:

Single Entry Point: src/index.ts contains the entire server implementation using:

@modelcontextprotocol/sdk for MCP server functionality
@google-analytics/data for GA4 API access
googleapis for Google Cloud authentication

Server Pattern: The server uses:

StdioServerTransport for communication
Request handlers for ListToolsRequestSchema and CallToolRequestSchema
Environment variable validation on startup

Tool Implementation

The server exposes 5 main tools through the MCP protocol:

runReport - Generic analytics report runner with custom dimensions and metrics
getPageViews - Page view metrics with optional dimensions
getActiveUsers - Active and new user counts over time
getEvents - Event tracking with optional event name filtering
getUserBehavior - Session duration, bounce rate, and sessions per user

Each tool follows the pattern:

Date range validation (YYYY-MM-DD format)
Google Analytics API call via analyticsDataClient.runReport()
JSON response formatting
Comprehensive error handling with McpError

Environment Requirements

The server requires these environment variables:

GOOGLE_CLIENT_EMAIL - Service account email
GOOGLE_PRIVATE_KEY - Service account private key
GA_PROPERTY_ID - Google Analytics 4 property ID

Read the full file on GitHub · 81 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 81 lines · 663 tokens per session scan A 1ffa6118d460

Subscribe to this mod's changes

mcp-server-google-analytics CLAUDE.md is an instructions file published in the GitHub repository ruchernchong/mcp-server-google-analytics (70 stars, last pushed 1y ago), licensed MIT. It adds 663 tokens to every session, about $0.0027 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics

mcp-server-google-analytics CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp-server-google-analytics CLAUDE.mdruchernchong/mcp-server-google-analytics	Instructions file	70	1y ago	MIT	A	663	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

mcp-server-google-analytics: Instructions file for Claude Code