Skip to main content
Glama
Sign In
jabeer4148-ops

google-measurement-mcp

by jabeer4148-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to google-measurement-mcp

No user-submitted related servers found.

    Related Servers

    • ga4-seo-mcp

      GermaniU
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to plan and, only when writes are explicitly enabled, apply a site's Google Analytics 4 and Search Console measurement setup — property and web stream creation, key events, custom dimensions, DNS verification, sitemap submission and a PageSpeed baseline — while remaining read-only by default.
      24
      182 PyPI
      1
      MIT

    • google-marketing

      omarmfouad25
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      4
      MIT

    • Google Webmaster MCP

      ehukaimedia
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Google Tag Manager, Google Search Console, and Google Analytics (GA4) through unified access to tags, search performance data, URL inspection, sitemaps, and analytics reporting.
      7 npm
      ISC

    • ga4-mcp-server

      dienhokhanh
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query Google Analytics 4 properties for standard, pivot, realtime, and batched reports, discover accounts, properties, and metadata, and optionally manage custom dimensions, metrics, and key events.
      14
      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

    A4.2/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool is namespaced by Google product (ga4_, gsc_, gtm_) and targets a distinct resource or action; the only close pair, gsc_search_analytics_query and gsc_compare_periods, is clearly differentiated by purpose and output. The gtm_list_* family covers separate collections (accounts, containers, workspaces, tags, triggers, variables), so an agent should not confuse them.

    Naming Consistency4/5

    The set is uniformly snake_case and strongly patterned: ga4_/gsc_/gtm_ prefixes with list_ for collection reads and get_/run_/inspect_/compare_ for actions. Minor deviations such as gsc_search_analytics_query (noun-style) and gmcp_diagnostics (no action verb) keep it from a perfect score.

    Tool Count4/5

    Twenty tools is at the high end, but the number is reasonable for a server spanning three distinct Google products (GA4, Search Console, Tag Manager) plus diagnostics. Each cluster has enough tools to support real read-only workflows without feeling padded.

    Completeness4/5

    The read-only measurement surface is largely covered: GA4 has metadata/reporting/realtime/discovery, Search Console has search analytics/sitemaps/URL inspection, and GTM has account-through-entity listing plus live/version comparison. Minor gaps remain, such as no GTM built-in variable tool or GTM write/publish operations, but these appear to be intentionally out of scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources