Skip to main content
Glama
Google Ads MCP

Google Ads MCP

Official

This is not an officially supported Google product.

Google Ads MCP

This is the Google Ads Model Context Protocol (MCP) server designed to provide a standardized way to integrate an LLM with Google Ads.

Continuous Integration Code Style: Google Conventional Commits pre-commit

Tools

Tool

Parameters

Description

list_accounts

Lists all available Google Ads accounts

search_stream

customer_id, query

Runs a Google Ads query

To learn more about GAQL, try out the Google Ads Query Builder and ensure you have a valid query.

Related MCP server: @vibeads/mcp

Setup

Google Ads

Use this documentation to set up a service account for the Google Ads API client library. This will require you to also set up a Google Cloud project and enable the Google Ads API. Create a google-ads.yaml file as defined here. Here's an example:

# google-ads.yaml
developer_token: INSERT_DEVELOPER_TOKEN_HERE
login_customer_id: INSERT_LOGIN_CUSTOMER_ID_HERE
json_key_file_path: JSON_KEY_FILE_PATH_HERE
use_proto_plus: true

Server

Run the Google Ads MCP server locally:

uv run server

Gemini CLI

Install the Gemini CLI by following the instructions here.

Add the Google Ads MCP server to your ~/.gemini/settings.json file. Here's an example:

{
  "mcpServers": {
    "googleAds": {
      "command": "uv",
      "args": [
        "--directory path/to/google_ads_mcp",
        "run",
        "server"
      ]
    }
  }
}

Learn more about MCP servers and Gemini CLI.

Contributing

Want to contribute? Learn more

Available Tools

2 tools
list_accountsD

Inputs: no named parameters.

search_streamD

Inputs: customer_id (required), query (required), login_customer_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.7/5.0

    Scored across 2 tools

    Disambiguation4/5

    Tool names suggest distinct functions (listing accounts vs. streaming search results), but lack of descriptions introduces slight ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern in snake_case (list_accounts, search_stream).

    Tool Count2/5

    Only 2 tools for a large platform like Google Ads is far too few, leaving most functionality uncovered.

    Completeness2/5

    The tool surface is severely incomplete, missing core operations like campaign management, budget control, or report generation.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      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
    • A
      license
      A
      quality
      B
      maintenance
      Enables interaction with Google Ads accounts through the Model Context Protocol, specifically tuned for local service businesses. Provides account health scoring, search term waste analysis, and diagnostic insights without requiring GAQL knowledge.
      11
      212 npm
      1
      MIT
    • 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