Skip to main content
Glama
googleads

google-ads-mcp

Official
by googleads

Related Servers

Alternatives to google-ads-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Google Ads API that enables LLMs to search and query Google Ads accounts, retrieve resource metadata, and generate keyword ideas.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Google Ads API MCP server that enables searching and listing accessible customers via natural language queries.
      2
      -
    • A
      license
      A
      quality
      F
      maintenance
      A read-write MCP server for managing Google Ads campaigns, ad groups, keywords, and ads via natural language.
      12
      2
      -
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that provides read and write access to Google Ads, allowing natural language management of campaigns, budgets, ad groups, bids, and keywords, with dry-run validation for safety.
      18
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing Google Ads campaigns through the official Google Ads API, covering accounts, campaigns, budgets, keywords, search terms, and keyword ideas. It provides tools for both reading and mutating live ads data, such as pausing campaigns, updating budgets, and adding keywords.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that exposes the Google Ads API to LLM clients, enabling account inspection, GAQL queries, performance reporting, and campaign management.
      -

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role: discovering customer IDs, fetching resource metadata, and running search queries. There is no functional overlap or ambiguity between them.

    Naming Consistency3/5

    Two tools follow a resource_action pattern (customers_list_accessible_customers, metadata_get_resource_metadata), but search_search breaks the pattern with a redundant verb and no resource prefix. The inconsistency is noticeable but not chaotic.

    Tool Count4/5

    With 3 tools, the surface is small but well-scoped for a read-only Google Ads querying server. It avoids bloat, though a bit thin for broader Ads management.

    Completeness4/5

    The toolset covers the full query workflow: authenticate/discover customers, discover queryable fields via metadata, and execute searches. Mutation capabilities are absent, but the server appears intentionally focused on querying, so no critical dead ends exist for that scope.

    Maintenance

    ActivityActive
    ResponsivenessResponsive