Skip to main content
Glama
Johansebastian96

Google Ads MCP Server

Related Servers

Alternatives to Google Ads MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs and AI agents to query and explore Google Ads accounts and API resources through MCP tools and resources, including account information, resource metadata, metrics, segments, and release notes.
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and AI agents to query Google Ads accounts via the Google Ads API, including searching account data, retrieving resource metadata, and accessing API discovery documents, metrics, segments, and release notes.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and AI agents to query Google Ads accounts, inspect resource metadata, list accessible customers, and retrieve reporting metrics, segments, discovery documents, and release notes via the Google Ads API.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query campaign performance, metrics, audiences, and geography, and to analyze budgets, wasted spend, and account health through natural language.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language querying of Meta/Facebook Ads data via the Graph API, including ad accounts, campaigns, ad sets, spend, and performance metrics.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing and analyzing ad accounts in plain language from AI assistants, including cross-account performance reports, keyword research, GAQL queries, and safe previewed changes.
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing accessible customers, discovering resource metadata, and executing a search query. Their descriptions reinforce the boundaries, and there is no overlap in functionality.

    Naming Consistency4/5

    All tools use snake_case with a category prefix (customers_, metadata_, search_), and the first two follow a prefix_verb_noun pattern. However, 'search_search' is redundant and breaks the pattern, and the first two repeat the category noun inside the object.

    Tool Count4/5

    Three tools is minimal but each earns its place in a read-only query workflow: discover customers, discover fields, and query data. For a server named 'Google Ads MCP Server', however, it feels thin given the breadth of the Ads API.

    Completeness4/5

    The surface covers the essential steps for querying Google Ads data: finding customer IDs, discovering selectable/filterable fields, and running searches. It lacks any write or mutation operations, which may be a gap if broader ad management is expected.

    Maintenance

    ActivityActive
    ResponsivenessNo issues