tracking-stack-mcp
Related Servers
Alternatives to tracking-stack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables managing Google Tag Manager and Google Analytics 4 through natural language, with tiered read/write/destructive safety controls including dry-run writes and two-phase confirmations for destructive actions.81MIT
- FlicenseNot gradedqualityCmaintenanceEnables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to manage Google Tag Manager accounts and containers through the Tag Manager API v2, covering account/container discovery, workspace creation and syncing, CRUD on tags, triggers, variables, and folders, built-in variable control, version snapshots, and guarded publishing. It authenticates with a user's own Google identity (or a service-account fallback), honors API quota limits, and writes a redacted SQLite debug log of every tool call and API request.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI apps to plan, build, audit, and report on Google Ads, GA4, Search Console, and Tag Manager accounts through natural language. Accounts are read-only by default, and every change is validated in a preview, applied only after confirmation, logged, and reversible.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and manage Genesys Cloud resources such as queues, skills, users, wrap-up codes, Architect flows, and outbound campaign cadences, while deliberately preventing deletes and leaving campaigns off until humans start them.-
- AlicenseNot gradedqualityBmaintenanceLets AI assistants design and provision Twilio contact-center infrastructure such as TaskRouter workspaces, activities, queues, workflows, and Studio IVR drafts from natural-language requests. All writes require confirmation, while dangerous actions like deleting resources, sending messages, buying numbers, pointing numbers, or starting calls remain blocked.62 npm2MIT
TDQS
Scored across 7 tools
Every tool has a unique vendor prefix (wc, ga4, gtm) combined with a distinct action/resource pair. The list_* and create_* tools are clearly separated, and wc_create_profile is unambiguous relative to wc_create_account.
All tools follow the consistent [vendor]_[verb]_[resource] pattern with lowercase snake_case. List verbs are plural and create verbs are singular, with no mixed conventions or vague action names.
Seven tools is well-scoped for a tracking-stack provisioning server covering three platforms. Each list/create pair earns its place, and the extra wc_create_profile is justified by the distinct resource type.
The set covers the core list-and-create lifecycle for WhatConverts, GA4, and GTM resources, including duplicate guards and dry-run defaults. Minor gaps exist around updates/deletes and GTM publishing, but the primary provisioning workflow is complete enough for agents to accomplish real setup tasks.