We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Google Ads, verified

MCP server by Google · Verified

Query Google Ads accounts with GAQL and inspect campaign data and performance metrics through the Google Ads API.

Runs locally (Runs on your machine: its page has the install command)Runs with pipxNeeds an API key

Install Google Ads

Runs on your machine. Your client starts it with this command:

pipx run google-ads-mcp

Needs pipx (Python) on your computer. The setup steps below show where the command goes in each client.

  • GOOGLE_ADS_DEVELOPER_TOKEN secret optional Google Ads API developer token.
  • GOOGLE_PROJECT_ID Google Cloud project ID (credentials come from ADC or GOOGLE_APPLICATION_CREDENTIALS).

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/google-ads

About

Connects to the Google Ads API so an assistant can search account data, run GAQL queries, look up resource metadata and list the customer accounts the signed-in user can access. Resources expose the API discovery document, available metrics and segments, and release notes.

Runs locally over stdio with pipx (pipx run google-ads-mcp). It needs Google credentials (Application Default Credentials or a credentials file) and a Google Cloud project with the Google Ads API enabled and at least Explorer access for production accounts. An optional OAuth proxy mode serves streamable HTTP.

What you can do

  • Run searches and GAQL queries against Google Ads accounts
  • Get metadata and available fields for a Google Ads resource such as campaign
  • List customer accounts accessible to the authenticated user
  • Read the Google Ads API discovery document, metrics and segments
  • Read the latest Google Ads API release notes
  • Enable or rename tools through a tools_config.yaml file

Tools

Google Ads lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • List the Google Ads customer accounts I can access

  • Show clicks, cost and conversions per campaign for the last 30 days

  • What fields can I query on the ad_group resource?

  • Which campaigns had the highest cost per conversion last week?

Set up

Every client starts Google Ads on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio google-ads --env "GOOGLE_ADS_DEVELOPER_TOKEN=<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>" --env "GOOGLE_PROJECT_ID=<YOUR_GOOGLE_PROJECT_ID>" -- pipx run google-ads-mcp
  1. Start Claude Code and type /mcp. google-ads should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_PROJECT_ID": "<YOUR_GOOGLE_PROJECT_ID>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs pipx (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_PROJECT_ID": "<YOUR_GOOGLE_PROJECT_ID>"
      }
    }
  }
}

Needs pipx (Python) on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "google-ads": {
      "type": "stdio",
      "command": "pipx",
      "args": [
        "run",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${input:google-ads-developer-token}",
        "GOOGLE_PROJECT_ID": "<YOUR_GOOGLE_PROJECT_ID>"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "google-ads-developer-token",
      "description": "GOOGLE_ADS_DEVELOPER_TOKEN",
      "password": true
    }
  ]
}

Needs pipx (Python) on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_PROJECT_ID": "<YOUR_GOOGLE_PROJECT_ID>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add google-ads --env "GOOGLE_ADS_DEVELOPER_TOKEN=<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>" --env "GOOGLE_PROJECT_ID=<YOUR_GOOGLE_PROJECT_ID>" -- pipx run google-ads-mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.google-ads]
command = "pipx"
args = ["run", "google-ads-mcp"]
env = { GOOGLE_ADS_DEVELOPER_TOKEN = "<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>", GOOGLE_PROJECT_ID = "<YOUR_GOOGLE_PROJECT_ID>" }

Needs pipx (Python) on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "GOOGLE_ADS_DEVELOPER_TOKEN=<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>" -e "GOOGLE_PROJECT_ID=<YOUR_GOOGLE_PROJECT_ID>" google-ads pipx run google-ads-mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_PROJECT_ID": "<YOUR_GOOGLE_PROJECT_ID>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs pipx (Python) on your computer. Replace the placeholders with your own values.

Embed

Show Google Ads in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Google Ads on mcp.tc](https://mcp.tc/i/google-ads/badge.svg)](https://mcp.tc/i/google-ads)
HTML
<a href="https://mcp.tc/i/google-ads"><img src="https://mcp.tc/i/google-ads/badge.svg" alt="Google Ads on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/google-ads.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/google-ads" title="Google Ads on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/google-ads.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google Ads card to your site.

Markdown
Add the mcp.tc card for Google Ads, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/google-ads.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="google-ads"><a href="https://mcp.tc/i/google-ads">Google Ads on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Google Ads on mcp.tc](https://mcp.tc/i/google-ads/badge.svg)](https://mcp.tc/i/google-ads)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its PyPI package: each new version shows up here, with edits by its owner.

Follow Google Ads and we’ll email you when something changes.

  1. , Automatic check

    New version 0.0.6 (was 0.0.5). Read from PyPI.

  2. , Automatic check

    New version 0.0.5 (was 0.0.4). Read from PyPI.

  3. , Automatic check

    Tracking started: version 0.0.4.

FAQ

Can I paste mcp.tc/i/google-ads into my MCP client?

No. Google Ads runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is pipx run google-ads-mcp.

Does Google Ads need an API key?

Yes. It reads GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_PROJECT_ID from its environment, and GOOGLE_ADS_DEVELOPER_TOKEN is a secret. Put the value in your client’s config on your own machine, never in a shared file.

Is Google Ads a remote or a local server?

Local. Your client starts it as a process on your computer with pipx run google-ads-mcp, which needs pipx (Python).

What can Google Ads do?

You can run searches and GAQL queries against Google Ads accounts, get metadata and available fields for a Google Ads resource such as campaign and list customer accounts accessible to the authenticated user.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to Google Ads?

Partly. It runs on your computer, so we follow its PyPI package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Google Ads’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Google. This page was built from Google Ads’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.