Skip to main content
Glama
LucasSantana-Dev

Google Ads MCP

by LucasSantana-Dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Google Ads MCP

No user-submitted related servers found.

    Related Servers

    • Google Ads MCP

      danielpopamd
      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

    • Google Ads MCP Server (Fork

      mathiaschu
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to manage Google Ads accounts by providing tools for querying account data and performing write operations such as updating campaign budgets, statuses, and bidding strategies.
      2
      Apache 2.0

    • Google Ads

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables full Google Ads management through natural language, including reading campaigns, performance, ROAS, keywords, and search terms, as well as pausing, enabling, removing, and creating campaigns, ad groups, ads, keywords, budgets, and responsive search ads.
      MIT

    • mcp-gads

      pijusz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and managing Google Ads campaigns, keywords, assets, and more via natural language, with support for multiple MCP clients.
      84 npm
      1
      MIT

    • Google Ads MCP Server

      saikrishna406
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage, report, and analyze Google Ads campaigns securely with encrypted multi-client support, real-time API integrations, and audit trail logging.
      24 npm
      MIT
    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 31 tools

    Disambiguation5/5

    Every tool targets a distinct resource or action (e.g., create_ad vs. create_campaign, get_keywords vs. get_recommendations). No two tools have overlapping purposes, and even similar verbs like 'enable' and 'pause' are clearly separated by entity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_campaign, get_keywords, pause_ad). Verbs like 'apply', 'dismiss', 'generate', 'list', 'run' are distinct and appropriately used. No mixing of casing or other conventions.

    Tool Count5/5

    With 31 tools, the server covers a broad range of Google Ads operations without becoming unwieldy. Each tool serves a specific purpose, and the count is reasonable given the complexity of the domain.

    Completeness2/5

    The toolset lacks update operations for most entities (e.g., no update_ad, update_campaign, update_ad_group) and no removal tools. While raw GAQL queries can fill some gaps, the surface is incomplete for standard lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources