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

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a distinct concern: customer discovery, schema/metadata discovery, and data retrieval. There is no overlap in purpose or output type.

    Naming Consistency4/5

    All names are snake_case and generally follow a {namespace}_{verb}_{object} pattern, but `search_search` is redundant and lacks an object, while the others include explicit objects. This is a minor inconsistency rather than a chaotic mix.

    Tool Count5/5

    Three tools is the minimal viable set for a read-only Google Ads query server: list customers, discover fields, and run queries. Each tool is essential and there are no filler or redundant tools.

    Completeness5/5

    The core workflow is fully covered: get customer IDs, discover valid fields via metadata, then search using those fields. For a query-focused MCP server there are no dead ends; mutation endpoints are outside the apparent scope.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources