google-ads-mcp-server

<div align="center">

# Google Ads MCP server

### Turn Google Ads questions into useful answers.

Explore performance, research keywords and prepare campaign changes from your MCP client.

[![Release](https://img.shields.io/github/v/release/get-mcp-ads/google-ads-mcp-server?color=2448e5)](https://github.com/get-mcp-ads/google-ads-mcp-server/releases/latest)
[![CI](https://github.com/get-mcp-ads/google-ads-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/get-mcp-ads/google-ads-mcp-server/actions/workflows/ci.yml)
[![Smithery](https://smithery.ai/badge/hello-6k33/getmcpads-google-ads)](https://smithery.ai/servers/hello-6k33/getmcpads-google-ads)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
[![Node](https://img.shields.io/badge/node-%E2%89%A522.12-brightgreen.svg)](package.json)

[Watch the demo](https://www.getmcpads.com/home/film/get-mcp-ads-film-1080p.mp4) · [What's new](#whats-new) · [Install](#install-this-release) · [Tool reference](#tools) · [Try hosted getmcpads](https://www.getmcpads.com/tools/google-ads?utm_source=github&utm_medium=readme&utm_campaign=google-ads)

[![Watch the getmcpads product demo: campaign review in Claude](https://www.getmcpads.com/home/film/poster-rich.webp)](https://www.getmcpads.com/home/film/get-mcp-ads-film-1080p.mp4)

**[Play the 27-second product film](https://www.getmcpads.com/home/film/get-mcp-ads-film-1080p.mp4)**

</div>

The film demonstrates hosted getmcpads with staged data. Its creative galleries and MCP Apps interface belong to the hosted product. This repository provides the standalone native API tools.

**35 read tools** · **10 write tools**, disabled by default.

Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.

## What's new

**[v2.0.1: Native tools and security update](https://github.com/get-mcp-ads/google-ads-mcp-server/releases/tag/v2.0.1) · September 20, 2026**

- Add descending image/video asset pagination.
- Add account-scoped upload processing reads and return the native upload ID.
- Retain API v25, standalone MCC discovery and credential redirect protection.
- Require Node.js 22.12 or newer and check Node 22/24 in CI.
- Update vulnerable dependencies and regenerate the MCP catalog.

[Full changelog](CHANGELOG.md) · [Source synchronization details](SOURCE_SYNC.md) · [All releases](https://github.com/get-mcp-ads/google-ads-mcp-server/releases)

### Upgrade notes

Requires **Node.js 22.12 or newer**. CI covers Node 22 and 24. Version 2.0.1 drops Node 18 and 20 support. Read the current tool schemas before reusing saved arguments. Writes remain optional and require explicit confirmation. Hosted creative integrations and MCP Apps UI are outside this release.

## Install this release

This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned `npx` examples later in this document select the version currently available on npm.

```bash
git clone --branch v2.0.1 --depth 1 https://github.com/get-mcp-ads/google-ads-mcp-server.git
cd google-ads-mcp-server
npm ci
npm run build
```

Configure your MCP client to run `node` with the absolute path to `dist/cli.js` and the platform credentials documented below.

> **Prefer a managed connection?** [Use Google Ads with hosted getmcpads](https://www.getmcpads.com/tools/google-ads?utm_source=github&utm_medium=readme&utm_campaign=google-ads). Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.

## What you get

| | |
|---|---|
| **35 read tools** | Campaigns, ad groups, budgets, bidding strategies, search terms, landing pages, Performance Max assets and placements, Shopping, recommendations, change history |
| **10 write tools** | Off by default. Status, budgets, bids, schedules, renames, campaign creation. Each one **previews before it applies** |
| **Full Keyword Planner** | Keyword ideas, historical metrics, forecasts, ad group themes, geo target suggestions |
| **130 metrics, 84 dimensions** | With a compatibility matrix that catches invalid combinations before they hit the API |
| **5 resources** | Live catalogues the model can read: metrics, dimensions, compatibility rules, 11 workflow recipes |
| **GAQL and beyond** | `google_ads_run_gaql` for raw queries, and `google_ads_run_readonly_rpc` for the services GAQL cannot reach |

### You do not need to know GAQL

The Google Ads API is queried with GAQL, its own query language, and most of its surface is
only reachable that way. This server carries the metric and dimension catalogues, so the model
asks for `cost` and `conversions` by name and the server writes the query.

`google_ads_validate_query` lets it check a combination before spending a call on it, and
`google_ads_run_gaql` is still there when you want to write GAQL yourself.

### Keyword Planner is not in GAQL

Keyword ideas, historical volumes and forecasts live in a separate RPC service that GAQL
cannot reach at all. Same for Reach Planner, audience insights and benchmarks. This server
covers them through `google_ads_run_readonly_rpc` and dedicated tools.

---

## Getting credentials

This is the heaviest setup of any advertising platform. Four values are needed, and one of
them requires a review by Google. Budget an hour the first time.

### 1. Developer token

From a **manager (MCC) account**, open **Tools → API Center** and apply for a token.
It starts at *Test Account* level, which only reaches test accounts. Apply for
**Basic Access** to reach live accounts. Google reviews the application, which can take a
few days.

📖 [Developer token documentation](https://developers.google.com/google-ads/api/docs/get-started/dev-token)

### 2. OAuth client

In a [Google Cloud project](https://console.cloud.google.com/), enable the **Google Ads API**,
then create an OAuth client under **APIs & Services → Credentials**. Choose **Desktop app**
for local use. Note the **client ID** and **client secret**.

### 3. Refresh token

Run the OAuth consent flow once, signed in as the Google account that can see your ad
accounts, and keep the **refresh token** it returns. Google's own helper script does this in
one command.

📖 [OAuth desktop flow](https://developers.google.com/google-ads/api/docs/oauth/cloud-project)

**The refresh token does not expire.** It is the sensitive value here: anyone holding it can
mint access tokens indefinitely. Treat it like a password, and use an OAuth client dedicated
to this server so you can revoke it on its own.

### 4. Login customer ID, if you use a manager account

If the accounts you query sit under an MCC, set `GOOGLE_ADS_LOGIN_CUSTOMER_ID` to the manager
account ID. Dashes are accepted and stripped. Skip it for a standalone account.

You can also leave it unset. Google refuses any request against a managed account unless the
call names its manager, with a `USER_PERMISSION_DENIED` that mentions neither the account nor
the manager, so it reads as missing access rather than as a missing header. When the variable
is unset and the account you query is not directly accessible, the server asks the managers it
can reach which accounts they hold, and announces the one that holds yours. The answer is
resolved once and kept for the life of the process.

Setting the variable is still faster: it skips that discovery entirely, and it is the right
choice when every account you query sits under the same MCC.

Run **`google_ads_health_check`** as your first call. It verifies all four credentials, lists
the accounts you can actually reach, and reports what is missing, without printing any secret.

---

## Setup

### Claude Desktop

`~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):

```json
{
  "mcpServers": {
    "google-ads": {
      "command": "npx",
      "args": ["-y", "@getmcpads/google-ads-mcp-server"],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "your-developer-token",
        "GOOGLE_ADS_CLIENT_ID": "your-client-id",
        "GOOGLE_ADS_CLIENT_SECRET": "your-client-secret",
        "GOOGLE_ADS_REFRESH_TOKEN": "your-refresh-token"
      }
    }
  }
}
```

Restart Claude Desktop. Ask it: *"list my Google Ads accounts"*.

### Claude Code

```bash
claude mcp add google-ads --env GOOGLE_ADS_DEVELOPER_TOKEN=... --env GOOGLE_ADS_CLIENT_ID=... --env GOOGLE_ADS_CLIENT_SECRET=... --env GOOGLE_ADS_REFRESH_TOKEN=... -- npx -y @getmcpads/google-ads-mcp-server
```

### Cursor

`.cursor/mcp.json` in your project, same shape as the Claude Desktop config above.

### From source

```bash
git clone https://github.com/get-mcp-ads/google-ads-mcp-server.git
cd google-ads-mcp-server
npm install && npm run build
cp .env.example .env   # then fill in your credentials
npm start
```

### Configuration

| Variable | Default | Meaning |
|---|---|---|
| `GOOGLE_ADS_DEVELOPER_TOKEN` | none | **Required.** From the API Center, Basic Access or above |
| `GOOGLE_ADS_CLIENT_ID` | none | **Required.** OAuth client ID |
| `GOOGLE_ADS_CLIENT_SECRET` | none | **Required.** OAuth client secret |
| `GOOGLE_ADS_REFRESH_TOKEN` | none | **Required.** From the consent flow |
| `GOOGLE_ADS_LOGIN_CUSTOMER_ID` | none | Optional. Manager (MCC) account ID. Resolved automatically when unset |
| `GOOGLE_ADS_ENABLE_WRITES` | *unset* | Set to `1` to register the 10 write tools |
| `LOG_LEVEL` | `info` | `debug`, `info`, `warn`, `error` |

Check your setup at any time:

```bash
npm run doctor
```

---

## Writes, and why they preview first

Write tools are **disabled by default**. Enable them with `GOOGLE_ADS_ENABLE_WRITES=1`.
Google's own server has none at all, so this is the part to read carefully.

When enabled, ev