Skip to main content
Glama
dhawalshah

google-tag-manager-mcp

by dhawalshah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to google-tag-manager-mcp

No user-submitted related servers found.

    Related Servers

    • unboundai-gtm-mcp-server

      tijevlam
      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
      67 npm
      Apache 2.0

    • GTM MCP Server

      pouyanafisi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Google Tag Manager API v2, enabling programmatic management of accounts, containers, workspaces, tags, triggers, variables, and version workflows.
      13 npm
      14
      MIT

    • tagmanager-mcp

      jinchliu
      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

    • Wascer GTM MCP Server

      soureiBR
      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
      -

    • Google Tag Manager MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the Google Tag Manager API v2, enabling natural-language management of containers, workspaces, tags, triggers, variables, and publishing. It handles OAuth authentication and built-in rate limiting for the strict GTM API quota.
      19
      120 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool is explicitly scoped to a distinct GTM entity (account, container, workspace, tag, trigger, etc.), with names like gtm_tag and gtm_trigger making the target resource clear. Despite shared CRUD actions, the entity distinction eliminates any ambiguity.

    Naming Consistency5/5

    All tools follow the consistent pattern gtm_<entity> in snake_case, and actions within each tool use standard verbs (list, get, create, update, remove, revert). This uniform naming convention makes the tool set predictable and easy to navigate.

    Tool Count4/5

    At 18 tools, the count is on the higher end of the typical range, but it is justified by the breadth of GTM's API which includes many distinct entity types. Each tool earns its place by covering a unique resource, so the count feels appropriate for the domain's complexity.

    Completeness5/5

    The server covers all major GTM entities including accounts, containers, workspaces, tags, triggers, variables, folders, clients, zones, templates, transformations, destinations, environments, versions, and user permissions. It also includes built-in variables and version headers, providing comprehensive lifecycle management with no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources