Skip to main content
Glama
apexradius

mcp-google-ads

by apexradius

Related Servers

Alternatives to mcp-google-ads

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server that provides tools and resources for interacting with Google Ads API, enabling search, metadata retrieval, and account management through natural language.
      3
      2,765 PyPI
      963
      Apache 2.0
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      MCP server to read and manage Google Ads accounts via GAQL queries, campaign/ad group/keyword operations, and safe write support with draft-confirm flow.
      16
      38 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Google Ads MCP server providing ~47 tools for full read/write access to Google Ads accounts, including campaign management, ad creation, keyword management, and reporting.
      2
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Multi-user Google Ads MCP server with OAuth-per-user auth, Firestore token storage, raw GAQL queries, and 10+ extra reporting tools beyond the official server.
      13
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized users to securely connect to and manage their Google Ads accounts through MCP clients, with support for campaigns, ad groups, ads, keywords, reporting, and billing. Runs as a remote multi-user server on Cloudflare Workers with per-user authentication and safety controls.
      -

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools are clearly distinct by entity (accounts, campaigns, keywords, ads) and action (list, get, set, compare). However, list_accounts and list_customers both list accounts with subtle differences (configured vs accessible) that could cause confusion.

    Naming Consistency4/5

    Tool names predominantly follow a verb_noun pattern (list_*, get_*, set_*). The deviations are 'compare_periods' (verb_noun but not get/list) and 'search_terms_report' (noun phrase without a verb), but the overall pattern is still readable and predictable.

    Tool Count5/5

    Ten tools is well within the ideal range for a domain-specific server. Each tool covers a distinct aspect of Google Ads reporting and account management, and none feel redundant or excessive.

    Completeness4/5

    The server provides comprehensive read/reporting coverage: account listing, summaries, campaign/keyword/ad performance, search terms, and period comparison. It lacks management operations like creating or updating campaigns, but this seems intentionally scoped to analytics and account selection, so the gaps are minor.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues