Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

Related Servers

Alternatives to Google Growth MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Unifies Google Ads, Tag Manager, Search Console, and GA4 into a single MCP server, enabling reporting, monitoring, campaign/tag/property creation, and live mutations with dry-run safety.
      94
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code, Claude Desktop, and Cursor to query and manage Google Search Console, GA4, and PageSpeed Insights data, including SEO reporting, URL index status, sitemap management, analytics reports, and Core Web Vitals.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Production-grade MCP server for the Google Tag Manager API v2 with read-only GA4 (Admin + Data API) tooling. 107 tools covering the full GTM surface, including server-side containers. Ships read-only: writes, publishes, and deletes are each gated behind separate opt-in flags, every mutation requires per-call confirmation, and a dry-run mode simulates changes. Includes container audits
      203
      663 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a read-only set of Google Ads query tools (GAQL search, resource metadata, and accessible customer listing) to Claude.ai remote connectors, with enforced read-only guarantees, OAuth 2.1 with fixed credentials and PKCE, persistent tokens, and a stateless /mcp endpoint in a single Docker image.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A production-oriented, read-only Google Search Console MCP server and TypeScript SDK for Claude, Cursor, VS Code, and other MCP clients. Query real Search Console data, inspect indexed URLs, review sitemaps, compare periods, and surface transparent SEO opportunities without handing private data to a third-party SaaS.
      20
      MIT

    TDQS

    A3.5/5.0

    Scored across 30 tools

    Disambiguation4/5

    Tools are grouped by product prefix and mostly target distinct resources or actions, so an agent can usually choose correctly. Minor ambiguity exists across repeated auth-status tools and the two Keyword Planner tools (keyword ideas vs. historical metrics), but descriptions clarify them well.

    Naming Consistency5/5

    All tools use snake_case with a consistent product-prefixed pattern such as ads_, gtm_, ga4_, and search_console_. Actions are predictable within each group (list_, get_, create_, update_, delete_, run_, auth_status), making names easy to scan and infer.

    Tool Count4/5

    Thirty tools is heavy for a single MCP server, but the surface spans four distinct Google products, each with its own auth and resource lifecycle. The count is above the ideal 3–15 range but defensible given the multi-product scope, with only GTM feeling somewhat expansive.

    Completeness4/5

    The surface covers core workflows across all four products: Ads auth and keyword research, GTM full lifecycle from workspace creation to publishing, GA4 reporting, and Search Console analytics and inspection. Gaps are minor by comparison, such as no Ads campaign management or Search Console sitemap submission, but these are outside the mostly read-only/GTM-operational scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues