Skip to main content
Glama
Asaya-01

Google Ads MCP Server

by Asaya-01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Google Ads MCP Server

No user-submitted related servers found.

    Related Servers

    • google-ads-mcp

      clarkstamina-max
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and AI agents to query Google Ads accounts via the Google Ads API, including searching account data, retrieving resource metadata, and accessing API discovery documents, metrics, segments, and release notes.
      Apache 2.0

    • Google Ads MCP Server

      georgebrinckmann
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with Google Ads accounts via the Google Ads API, providing tools for account search, resource metadata retrieval, and customer listing, along with access to API discovery documents and reporting metrics.
      Apache 2.0

    • google-ads-mcp

      Reuben1987AI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and LLMs to interact with Google Ads accounts, allowing search, retrieval of resource metadata, and listing accessible customers via the Google Ads API.
      Apache 2.0

    • Google Ads MCP Server

      PradeepGontupuli
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs and AI agents to query and explore Google Ads accounts and API resources through MCP tools and resources, including account information, resource metadata, metrics, segments, and release notes.
      3
      Apache 2.0

    • Google Ads MCP Server

      noviq-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to interact with the Google Ads API to retrieve account information, list accessible customers, and query campaign performance. It allows users to manage and analyze Google Ads data through natural language interfaces.
      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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool has a distinct purpose: discovering customer IDs, retrieving resource metadata, and running queries. The boundaries are clear, though search_search is vague compared to the more descriptive tool names.

    Naming Consistency4/5

    All three follow a resource_action pattern (customers_list..., metadata_get..., search_search), which is predictable. However, search_search is redundantly named and the convention isn't perfectly uniform in rhythm.

    Tool Count3/5

    Three tools for the vast Google Ads API is thin. The generic search + metadata pattern is a defensible minimal design, but the surface is borderline sparse for the breadth of the domain.

    Completeness3/5

    The discovery-to-query workflow (customers -> metadata -> search) covers read access well, but there are no mutation tools (create/update/delete campaigns, budgets, etc.), a notable gap for the Google Ads domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources