Skip to main content
Glama
Google Tag Manager MCP

Google Tag Manager MCP

Related Servers

Alternatives to Google Tag Manager MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Google Tag Manager API, enabling users to manage containers, tags, and triggers through natural language using Google Application Default Credentials.
      18
      94 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Google Tag Manager API v2, enabling programmatic management of accounts, containers, workspaces, tags, triggers, variables, and version workflows.
      46 npm
      15
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      An MCP server for the Google Tag Manager API v2 that enables AI assistants to query GTM accounts, containers, tags, triggers, variables, and unpublished changes.
      24
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server for Google Tag Manager that enables AI assistants to manage GTM accounts, containers, tags, triggers, variables, and more via OAuth or service account authentication.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Google Tag Manager, offering tools to manage accounts, containers, workspaces, tags, triggers, and versions, with explicit confirmation for production-affecting actions.
      -

    TDQS

    A3.9/5.0

    Scored across 25 tools

    Disambiguation3/5

    The dedicated list/get tools (list_tags, list_triggers, list_variables, get_container, get_workspace) are clear, but the generic entity tools (get_resource, create_entity, update_entity, delete_entity) overlap heavily with the resource-specific ones, and it is not obvious when to use create_entity versus create_container/create_workspace. Multi-action tools (publish_version with publish/get/live, manage_built_in_variables with list/enable/disable) and six auth-related tools (set_client, start_login, finish_login, auth_status, setup_instructions, logout) further blur selection for an agent.

    Naming Consistency4/5

    Nearly all tools follow a snake_case verb_noun pattern (get_account, list_containers, create_workspace, delete_entity, publish_version), which is predictable and readable. Minor deviations exist: logout is a bare verb, auth_status is noun-first, and setup_instructions is a noun phrase, so naming is mostly but not perfectly consistent.

    Tool Count3/5

    At 25 tools this sits at the heavy end of the acceptable range for a domain with accounts, containers, workspaces, tags, triggers, variables, versions and publishing. However, six auth/setup tools plus a generic CRUD trio layered on top of resource-specific tools adds redundancy that inflates the surface beyond what the core GTM workflow needs.

    Completeness4/5

    Lifecycle coverage is strong: read/create/update/delete for tags, triggers and variables, plus workspaces, versions, publishing, built-in variables and full auth flow. Gaps are minor — no dedicated delete/update for containers, workspaces or accounts and no per-type get for tags/triggers — but raw_request serves as an escape hatch for environments, folders, templates, zones and these missing operations.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues