Provides integration with Google Analytics 4 (GA4) Admin and Google Tag Manager (GTM), allowing users to list GA4 accounts, properties, streams, and measurement IDs; create GA4 properties with web streams; list GTM accounts and containers; and create new GTM web containers without publishing.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@tracking-stack-mcp Create a new GA4 property and web stream for the Acme account"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for an agency's tracking-stack setup: WhatConverts, GA4 Admin, GTM.
Same write-safety contract as google-ads-mcp: every mutating tool is a dry-run
by default and executes only with confirmed: true; writes are rate-limited and logged
to ~/.local/state/tracking-stack-mcp/actions.jsonl.
Create-only by design. No delete, unlink, user-management, or GTM publish tools exist here. Removing things and publishing containers stays portal work.
Tool | Type | Description |
| Read | All WhatConverts accounts + profiles |
| ⚠️ Mutating | New WC account (dupe-name refusal) |
| ⚠️ Mutating | New profile; refuses if the name exists anywhere in the agency |
| Read | GA4 accounts, properties, streams + measurement IDs |
| ⚠️ Mutating | New GA4 property + web stream; returns |
| Read | GTM accounts + containers |
| ⚠️ Mutating | New web container; returns |
Related MCP server: enterprise-agent-lab
~/.config/tracking-stack-mcp/.env (chmod 600)WC_API_TOKEN=... # canonical copy lives in your secret manager
WC_API_SECRET=...
GOOGLE_CLIENT_ID=... # OAuth client (can reuse the google-ads-mcp client)
GOOGLE_CLIENT_SECRET=...
GOOGLE_REFRESH_TOKEN=... # must carry analytics.edit + tagmanager.edit.containers + tagmanager.readonly
GA4_DEFAULT_TIME_ZONE=America/Los_Angeles # optional, default UTC
GA4_INDUSTRY_CATEGORY=HOME_AND_GARDEN # optional, omitted if unsetMint the Google refresh token once with the OAuth playground or the google-ads-mcp
auth-setup pattern, adding the three scopes above. Never commit .env; never put these
values in the vault.
Create-only. No delete, unlink, user-management, or publish tools exist.
Dry run by default. Only a boolean confirmed: true executes; "true" does not.
Validated inputs. Names are non-empty strings; ids are integers or accounts/<id>;
stream URLs must be https://.
Duplicate-name refusal across the whole agency before any create.
Rate cap of 10 writes per rolling hour per process, checked after the confirmed branch.
Append-only action log of every executed write, refusal, and failure; never previews.
No tenant values in code. Time zone and industry category come from env.
"tracking-stack": {
"command": "node",
"args": ["/Users/<you>/Documents/Claude/tracking-stack-mcp/dist/index.js"]
}npm install && npm run buildRecent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Runtime permission, approval, and audit layer for AI agent tool execution.
Reliable async execution for agent tool calls: schema gating, retries, idempotency, audit trail.
Project-scoped marketing ops for agents: Bearer dpk_/dpa_ or OAuth, read and supervised write.
Governance runtime for compliance: verified, human-approved writes to a tamper-evident record.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jayweezy247/tracking-stack-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
