Skip to main content
Glama
anegash

Google Ads MCP Server

by anegash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Google Ads MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • google-ads-mcp

      aisandler
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Google Ads campaign reporting and management via Claude, enabling GAQL queries, performance metrics, and campaign modifications.
      6 npm
      MIT
    • LoomaScale Google Ads by loomascale

      LoomaScale Google Adsofficial

      loomascale
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Google Ads. Audit spend, find wasted budget, create campaigns, monitor performance, and optimize ads directly from ChatGPT, Claude, or any MCP-compatible client.
      MIT
    • adrex-ai by adrex-ai

      adrex-aiofficial

      adrex-ai
      A
      license
      B
      quality
      B
      maintenance
      Open-source MCP server for Google Ads (Meta Ads coming soon) that lets AI assistants manage ad campaigns, reporting, keywords, and targeting in plain English from any MCP client, with safety-first creation of paused campaigns.
      54
      56 npm
      3
      MIT

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

    C2.5/5.0

    Scored across 76 tools

    Disambiguation3/5

    Several tools overlap in purpose, such as create_sitelink_assets vs create_sitelink_extensions, create_callout_assets vs create_callout_extensions, and get_geographic_report vs get_geographic_performance, which could confuse an agent. However, most tools have distinct resource-action targets and descriptions likely help.

    Naming Consistency5/5

    All tools consistently follow a verb_noun snake_case pattern (e.g., list_accounts, get_campaigns, create_campaign, update_campaign_status). No mixed conventions or inconsistent verb styles.

    Tool Count1/5

    With 76 tools, the server far exceeds the reasonable range for a typical MCP server. Many tools are highly granular or redundant (e.g., duplicate extension creation methods), resulting in an overwhelming surface area.

    Completeness3/5

    The server covers a broad range of Google Ads features but lacks fundamental lifecycle operations such as deleting campaigns/ad groups/ads, updating ad groups, removing keywords, or retrieving single entities. Several resource types have create-only methods without corresponding read/update/delete tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources