Google Ads MCP Server

The Google Ads MCP Server is an implementation of the Model Context Protocol (MCP) that enables Large Language Models (LLMs), such as Gemini, to interact directly with the Google Ads API.

This is not an officially supported Google product.

Copyright Google LLC. Supported by Google LLC and/or its affiliate(s). This solution, including any related sample code or data, is made available on an “as is,” “as available,” and “with all faults” basis, solely for illustrative purposes, and without warranty or representation of any kind. This solution is experimental, unsupported and provided solely for your convenience. Your use of it is subject to your agreements with Google, as applicable, and may constitute a beta feature as defined under those agreements. To the extent that you make any data available to Google in connection with your use of the solution, you represent and warrant that you have all necessary and appropriate rights, consents and permissions to permit Google to use and process that data. By using any portion of this solution, you acknowledge, assume and accept all risks, known and unknown, associated with its usage and any processing of data by Google, including with respect to your deployment of any portion of this solution in your systems, or usage in connection with your business, if at all. With respect to the entrustment of personal information to Google, you will verify that the established system is sufficient by checking Google's privacy policy and other public information, and you agree that no further information will be provided by Google.

Follow these instructions to configure and run the Google Ads MCP Server.

This project needs Python 3.12 with pipx or uv.

This project uses uv for dependency management.

Install uv and then run the following command to install the required Python packages:

uv pip sync

This tool requires you to have a google-ads.yaml file with your Google Ads API credentials. By default, the application will look for this file in your home directory.

If you don't have one, you can generate it by running the following example from the google-ads-python library: authentication example

Make sure your google-ads.yaml file contains the following keys:

• client_id
• client_secret
• refresh_token
• developer_token
• login_customer_id (optional, but recommended)

Update your Gemini configuration to include the google-ads-mcp server. The following is an example of a local MCP server configuration:

{
  // Other configs...
  "mcpServers": {
    "GoogleAds": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/google-marketing-solutions/google_ads_mcp.git",
        "run-mcp-server"
      ],
      "env": {
        "GOOGLE_ADS_CREDENTIALS": "PATH_TO_YAML"
      },
      "timeout": 30000,
      "trust": false
    }
  }
}

Once the server is running, you can interact with it using the Gemini CLI. Type /mcp in Gemini to see the Google Ads API server listed in the results.

Update your Gemini configuration to include the google-ads-mcp server. [DIRECTORY] will be the absolute path to the project. The following is an example of a local MCP server configuration:

{
  // Other configs...
  "mcpServers": {
    "GoogleAds": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "[DIRECTORY]",
        "-m",
        "ads_mcp.server"
      ],
      "cwd": "[DIRECTORY]",
      "timeout": 30000,
      "trust": false
    }
  }
}

Once the server is running, you can interact with it using the Gemini CLI. Type /mcp in Gemini to see the Google Ads API server listed in the results.

You can then ask questions like:

• "list all campaigns"
• "show me metrics for campaign [CAMPAIGN_ID]"
• "get all ad groups"

To start the server directly, in the project path, run the following command:

uv run -m ads_mcp.server

The server will start and be ready to accept requests.

We welcome contributions! Please see our CONTRIBUTING.md guide for details.

Google Ads MCP Server is an open-source project licensed under the APACHE-2.0 License.

If you have any questions, suggestions, or feedback, please feel free to open an issue.