← ga-mcp-full

Privacy Policy

Last updated: 2026-06-09 · Source · Contact: ringo380@gmail.com

What ga-mcp-full is

ga-mcp-full is an open-source Model Context Protocol (MCP) server that exposes Google Analytics 4 Admin API and Data API endpoints as tools for AI assistants such as Claude Code, Claude Desktop, and Cursor. It runs entirely on the end user's own machine (stdio transport). There is no hosted backend operated by the project maintainers.

What data is accessed

When you authenticate, ga-mcp-full is granted two Google Analytics OAuth scopes — https://www.googleapis.com/auth/analytics.edit and https://www.googleapis.com/auth/analytics.readonly — together with the standard openid and email sign-in scopes (used only to show which Google account is connected). The Analytics scopes allow the tool to:

• Read property-, data-stream-, and account-level configuration of your GA4 properties.
• Read report data, realtime data, and metadata from your GA4 properties.
• Create, update, and delete property-level resources you explicitly request: custom dimensions, custom metrics, key events, audiences, data streams, Firebase/BigQuery/Google Ads links, and measurement protocol secrets.

All access is on-demand and initiated by the user of the AI assistant. The tool does not perform background access.

Where data is stored

• OAuth credentials (access + refresh tokens) are cached locally at ~/.config/ga-mcp/credentials.json on the end user's own machine, with file permissions 0600 (user-read/write only). They are never transmitted to the project maintainers or any third party.
• Google Analytics data (reports, configuration) retrieved through the tool is passed directly from Google's API to the local MCP client and then to the AI assistant you are using. ga-mcp-full itself does not log, retain, or redistribute this data.
• No server-side storage. The project maintainers do not operate any hosted service that receives your data or credentials. The shared OAuth client ID + secret bundled with the tool exist only to identify the software to Google's OAuth servers; they do not route traffic through any third-party server.

Data retention and deletion

OAuth tokens are retained on the local machine only until the user removes them. They are deleted when the user runs ga-mcp-full auth logout (or the equivalent /ga-mcp-full:auth-logout slash command), or when the ~/.config/ga-mcp/credentials.json file is manually removed. Revoking access at myaccount.google.com/permissions additionally invalidates the refresh token at Google's end so any remaining local copy is non-functional. No backup, archive, or off-machine copy of these credentials is created by ga-mcp-full.

Google Analytics data fetched at runtime is held only in process memory long enough to return the result to the AI assistant; it is not written to disk by ga-mcp-full and is discarded when the MCP subprocess exits.

Use of Google user data

ga-mcp-full uses Google user data solely to fulfill the user's tool requests within their AI assistant session. Specifically, ga-mcp-full does not:

• Sell, lease, or trade Google user data to any third party.
• Transfer Google user data to any third party for advertising, marketing, or remarketing purposes.
• Use Google user data to train or improve any general-purpose AI/ML model. (Tool results are passed to the AI assistant the user has chosen — e.g., Claude Code — whose handling is governed by that vendor's privacy policy. ga-mcp-full itself performs no model training, fine-tuning, or analytics on the data.)
• Use Google user data for credit assessment, lending, or any purpose unrelated to the user-initiated tool call.
• Allow humans associated with the project to read Google user data, except (a) the user themselves on their own machine, (b) with the user's explicit consent for support purposes, (c) for security investigations, or (d) where required by law.

What is transmitted

• To Google: OAuth authorization requests and GA4 Admin/Data API requests, originating from your local machine, using the credentials you granted at consent time.
• To your AI assistant: tool results (API responses) returned through the MCP stdio transport on your local machine.
• To the project maintainers: nothing. There is no telemetry, analytics, crash reporting, or usage tracking built into the tool.

Third-party services

• Google handles your OAuth consent, token issuance, and GA4 API requests. Google's privacy policy governs their processing of this data: policies.google.com/privacy
• Your AI assistant vendor (e.g., Anthropic for Claude Code) handles the AI-assistant side. Their privacy policy governs tool-result handling.

ga-mcp-full itself is an intermediary that runs on your machine and does not introduce additional data-collection relationships.

Why the analytics.edit and analytics.readonly scopes

The tool exposes ~30 GA4 Admin API and Data API operations. They map to two scopes, each the minimum its API accepts:

• analytics.edit (Admin API) covers the administrative read/write operations — create, update, and delete custom dimensions, custom metrics, key events, audiences, data streams, Firebase/BigQuery/Google Ads links, measurement-protocol secrets, and data-retention settings.
• analytics.readonly (Data API) covers the reporting operations (run_report, run_realtime_report). The GA4 Data API does not accept analytics.edit, so analytics.readonly is the minimum scope that enables reporting.

Google's OAuth model offers no finer-grained write scope below analytics.edit, and no single scope spans both the Admin write operations and the Data API reads, so both are requested. The tool requests no broader analytics scope and no restricted scopes. Users who only need read access may set up their own OAuth client limited to analytics.readonly via the environment-variable override documented in the project README.

Credential revocation

To revoke ga-mcp-full's access at any time:

1. Run /ga-mcp-full:auth-logout in Claude Code (or ga-mcp-full auth logout at the shell) to delete the local token cache.
2. Visit myaccount.google.com/permissions and remove "ga-mcp-full" from the list of apps with access to your account.

Either step alone is sufficient to end future access; both are recommended for defense in depth.

Changes to this policy

Changes are made by commit to PRIVACY.md in the source repository; this page is rendered from that canonical source. The "Last updated" date at the top reflects the most recent substantive change.

Questions

Email ringo380@gmail.com or open an issue at github.com/ringo380/ga-mcp-full/issues.