Skip to main content
Glama
burhan29ee

google-analytics-gtm-mcp

by burhan29ee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to google-analytics-gtm-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-gtm-ga4

      mharnett
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Google Tag Manager and GA4, enabling tag management, consent auditing, workspace versioning, and analytics reporting through natural language.
      11
      38 npm
      2
      MIT

    • gsc-mcp

      FlorianBruniaux
      A
      license
      B
      quality
      A
      maintenance
      MCP server providing 32 tools for Google Search Console and Google Analytics 4, enabling search analytics, URL inspection, indexing, and cross-platform analysis via natural language.
      43
      36 PyPI
      12
      MIT

    • mcp-server-google-analytics

      GunnarGriese
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing access to Google Analytics Data API, enabling LLMs to retrieve reports, real-time data, and metadata from GA4 properties.
      -

    • @ainative/gtm-mcp

      AINative-Studio
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Google Tag Manager and Google Ads, enabling AI agents to audit, fix, and manage GTM containers and Google Ads campaigns programmatically.
      42 npm
      MIT

    • Analytics MCP

      abhishekshankar
      A
      license
      Not graded
      quality
      D
      maintenance
      Automates Google Analytics 4 and Google Tag Manager setup, management, and health monitoring with blueprints, multi-environment support, and MCP tools for AI agents.
      MIT

    • mcp-site-analyst

      danishm
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that provides Google Analytics and Search Console data as tools for AI assistants, enabling natural language queries for web analytics, SEO performance, and site insights.
      13
      -
    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

    B3.2/5.0

    Scored across 40 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action. The gtm_ prefix cleanly separates GTM tools from GA4 tools, and each list/get/create/update/delete/send tool maps to a unique resource (reports, dimensions, metrics, key events, audiences, secrets, tags, triggers, variables, versions). There is no overlap or ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern, but the GA4 tools use bare verbs (list_, create_, archive_) while GTM tools are prefixed with gtm_ (gtm_list_, gtm_create_), which is a visible deviation. Also, 'get_property_details' doesn't align with 'list_account_summaries', 'send_ga4_event' and 'gtm_whoami' break the pattern, and archive vs delete is used inconsistently. Still, within each domain the pattern is fairly regular.

    Tool Count2/5

    40 tools is well above the 25+ threshold that typically feels too heavy for an MCP server. Even though the server covers two distinct APIs (GA4 and GTM), the number of tools will clutter the agent's context and many are narrowly scoped (e.g., separate create/update/delete for three GTM resources). The count is excessive for practical use.

    Completeness3/5

    The server covers a broad range of GA4 and GTM operations, but there are notable gaps: no update for custom dimensions/metrics (only archive for dimensions), no update/delete for key events, no update for audiences, no update for measurement protocol secrets, and no GTM container/workspace creation or deletion. These gaps are workable but represent missing lifecycle operations in the domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources