Skip to main content
Glama
googleads

google-ads-mcp

Official
by googleads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to google-ads-mcp

No user-submitted related servers found.

    Related Servers

    • Google Ads MCP Server

      qmedia-by
      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

    • gads

      n-asuy
      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
      -

    • Google Ads MCP Server

      MaxGhenis
      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
      -

    • google-ads-mcp-server

      burhan29ee
      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

    • Google Ads Campaign MCP

      clientskatbi
      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

    • Google Ads MCP Server

      pralayasimha23
      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.
      -
    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/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have clearly distinct purposes: discovering customer IDs, retrieving resource metadata, and executing queries. There is no overlap, though the generic name 'search_search' is slightly vague.

    Naming Consistency3/5

    All names use snake_case, but the pattern is inconsistent: 'customers_list_accessible_customers' and 'metadata_get_resource_metadata' include a resource prefix and redundant object, while 'search_search' repeats the verb and omits any prefix.

    Tool Count3/5

    Three tools is quite thin for the vast Google Ads API, but the search tool is broad enough to cover many query use cases. It's borderline under-scoped for the domain.

    Completeness2/5

    The surface is read-only and lacks any mutation, creation, or deletion operations, plus no customer detail retrieval beyond listing IDs. These are significant gaps for a general Google Ads server.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources