ga-gsc-analytics
Read-only integration with Google Analytics 4, enabling tools to run reports and retrieve analytics data.
Read-only integration with Google Search Console, enabling tools to query search analytics data.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ga-gsc-analytics
Read-only MCP server exposing Google Analytics 4 and Google Search Console data
(analytics.readonly + webmasters.readonly scopes) to Claude Code / Codex.
New here? Follow ONBOARDING.md for a zero-to-working walkthrough
(install Claude Code, get credentials, authorize, verify). The rest of this file is
reference material.
AI agents: this file doubles as
AGENTS.md— start here for setup, then readskills/analyze-ga-gsc/SKILL.mdfor how to use the tools (access checks, default date ranges, GA4 vs. GSC semantics, presentation handoff format). Never ask a user to paste credentials into chat.
Tools
analytics_auth_start/analytics_auth_status— local OAuth flow + status checkanalytics_list_sources— list GA4 properties and GSC sites available to the authorized accountga_run_report— run a GA4 reportgsc_query_search_analytics— query Search Console dataanalytics_presentation_snapshot— combined GA4 + GSC snapshot for reporting
Related MCP server: google-search-console-mcp-server
Setup (per user)
Each user authorizes with their own Google account and keeps their own local
token — never share client_secret.json secrets or tokens.json between machines.
Google Cloud OAuth client: create (or reuse an existing) OAuth 2.0 Desktop client in Google Cloud Console and download its
client_secret.json. If the consent screen is in "Testing" publishing status, add each new user's Google account as a test user first, or auth will fail with access-denied.Place the credentials at
~/.config/ga-gsc-analytics/client_secret.json(or pointGA_GSC_CLIENT_SECRETat a custom path).Grant data access: the authorizing Google account needs real permissions on the target GA4 property (Analytics Admin → Property Access Management) and the GSC site (Search Console → Settings → Users and permissions).
Build the server (only needed if you change
mcp/server.mjs; the repo ships a prebuiltmcp/server.bundle.cjs):pnpm install pnpm run build # bundles mcp/server.mjs -> mcp/server.bundle.cjsRegister the MCP server. Either:
Claude Code, user-level:
claude mcp add ga-gsc-analytics -- node /path/to/ga-gsc-analytics/mcp/server.bundle.cjsClaude Code / Codex, project-scoped: this repo already ships a relative
.mcp.json({"mcpServers": {"ga_gsc_analytics": {"command": "node", "args": ["./mcp/server.bundle.cjs"]}}}) — copy it into a project, or symlink/vendor this whole folder in, and it's picked up automatically when that project is opened.
Authorize: call the
analytics_auth_starttool from within your AI tool — it opens a local browser OAuth flow and writes~/.config/ga-gsc-analytics/tokens.json.Verify: call
analytics_auth_status(should reportauthorized: true), thenanalytics_list_sourcesto confirm the expected GA4 properties / GSC sites show up.
Config overrides
Env var | Default |
|
|
|
|
|
|
Development
pnpm run check # syntax check
pnpm test # node --test tests/*.test.mjsTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
Read-only Google Search Console and Google Analytics for AI agents.
Read-only Google Search Console, Bing, Google Analytics and privacy-friendly analytics for your AI.
Read-only access for your AI to Search Console, GA4, Google Ads, Meta Ads and your store's sales.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRead-only access to Google Analytics 4 reporting data, including traffic overview, top pages, traffic sources, and conversion events, supporting custom report queries via MCP.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to query Google Search Console search performance, inspect indexing, analyze sitemaps, and run SEO analyses such as cannibalisation detection, query clustering, and wins/losses, all with read-only access.20Apache 2.0
- AlicenseAqualityBmaintenanceEnables read-only access to Google Search Console data, including property discovery, search analytics queries, and URL inspection, through a security-focused interface.32,636 PyPI2MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to Google Analytics 4, Google Search Console, BigQuery saved queries, GitHub repository data, and Metricool status for SEO/SEM monitoring and analysis.-