MCP server for Google Tag Manager and GA4 that facilitates tag management, consent auditing, workspace versioning, and analytics reporting.
From the registry: GTM + GA4 MCP: tag management, consent auditing, workspace versioning, reports.
Please install the `gtm-ga4` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Google Cloud service account** — Create a GCP service account JSON key with GTM and GA4 access (https://cloud.google.com/iam/docs/service-accounts)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["mcp-gtm-ga4"]
- required environment variables:
- `GOOGLE_APPLICATION_CREDENTIALS`: Path to a GCP service account JSON key file (example: `/path/to/service-account.json`)
- `GTM_ACCOUNT_ID`: GTM account ID (example: `<your-gtm-account-id>`)
- `GTM_CONTAINER_ID`: GTM container ID (example: `<your-gtm-container-id>`)
- `GA4_PROPERTY_ID`: GA4 property ID (example: `<your-ga4-property-id>`)
- optional environment variables:
- `GTM_SANDBOX_WORKSPACE_ID`: Override workspace ID (auto-detects Default Workspace if omitted) (example: `<your-workspace-id>`)
- `MCP_SERVER_NAME`: Server name override (example: `neon-one-gtm`)
Note: Sandbox-safety: write operations refuse to target non-sandbox workspaces.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.GOOGLE_APPLICATION_CREDENTIALSrequiredPath to a GCP service account JSON key fileGTM_ACCOUNT_IDrequiredGTM account IDGTM_CONTAINER_IDrequiredGTM container IDGA4_PROPERTY_IDrequiredGA4 property IDTrending hip-hop artist momentum scores across four cultural dimensions.
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Official OpenMetadata MCP: governed context and business semantics for AI assistants and agents.