Google Ads

io.github.ZLeventer/google-ads-mcp · v1.0.1

MCP server for Google Ads — 22 tools for spend diagnosis, impression share, and asset performance.

Source code Set it up

Connect Runs on your machine

Terminal

claude mcp add google-ads-mcp -e GOOGLE_ADS_DEVELOPER_TOKEN=<GOOGLE_ADS_DEVELOPER_TOKEN> -e GOOGLE_ADS_CLIENT_ID=<GOOGLE_ADS_CLIENT_ID> -e GOOGLE_ADS_CLIENT_SECRET=<GOOGLE_ADS_CLIENT_SECRET> -e GOOGLE_ADS_REFRESH_TOKEN=<GOOGLE_ADS_REFRESH_TOKEN> -e GOOGLE_ADS_CUSTOMER_ID=<GOOGLE_ADS_CUSTOMER_ID> -e GOOGLE_ADS_LOGIN_CUSTOMER_ID=<GOOGLE_ADS_LOGIN_CUSTOMER_ID> -- npx -y @zleventer/[email protected]

claude_desktop_config.json

{
  "mcpServers": {
    "google-ads-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zleventer/[email protected]"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
        "GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
        "GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
        "GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<GOOGLE_ADS_LOGIN_CUSTOMER_ID>"
      }
    }
  }
}

~/.cursor/mcp.json

{
  "mcpServers": {
    "google-ads-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zleventer/[email protected]"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
        "GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
        "GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
        "GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<GOOGLE_ADS_LOGIN_CUSTOMER_ID>"
      }
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "google-ads-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@zleventer/[email protected]"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "<GOOGLE_ADS_DEVELOPER_TOKEN>",
        "GOOGLE_ADS_CLIENT_ID": "<GOOGLE_ADS_CLIENT_ID>",
        "GOOGLE_ADS_CLIENT_SECRET": "<GOOGLE_ADS_CLIENT_SECRET>",
        "GOOGLE_ADS_REFRESH_TOKEN": "<GOOGLE_ADS_REFRESH_TOKEN>",
        "GOOGLE_ADS_CUSTOMER_ID": "<GOOGLE_ADS_CUSTOMER_ID>",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "<GOOGLE_ADS_LOGIN_CUSTOMER_ID>"
      }
    }
  }
}

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server runs locally, so its tools are listed by your MCP client once it starts.

Environment variables

Name	Description
`GOOGLE_ADS_DEVELOPER_TOKEN` Required, secret	Google Ads developer token (apply at https://developers.google.com/google-ads/api/docs/get-started/dev-token)
`GOOGLE_ADS_CLIENT_ID` Required, secret	OAuth 2.0 client ID from Google Cloud Console
`GOOGLE_ADS_CLIENT_SECRET` Required, secret	OAuth 2.0 client secret from Google Cloud Console
`GOOGLE_ADS_REFRESH_TOKEN` Required, secret	OAuth 2.0 refresh token with https://www.googleapis.com/auth/adwords scope
`GOOGLE_ADS_CUSTOMER_ID` Required	Default Google Ads customer ID (numeric, no dashes). Can be overridden per tool call.
`GOOGLE_ADS_LOGIN_CUSTOMER_ID` Optional	Manager (MCC) account ID — required only if accessing accounts under an MCC

Details

Package	`@zleventer/[email protected]` (NPM, stdio)
First published	26 Apr 2026
Last updated	26 Apr 2026
Registry name	`io.github.ZLeventer/google-ads-mcp`

More search and web servers See all

Live status

Local install

Installed and run on your own machine, so there is no public endpoint to check.

Pair it with live search

Agents that use Google Ads often also need current facts. NestDaddy MCP gives your AI today's internet: web search, real-time breaking news and full page reading in one connector.

See NestDaddy MCP

For maintainers

[![NestDaddy MCP](https://nestdaddy.com/mcp/servers/io-github-zleventer-google-ads-mcp/badge.svg)](https://nestdaddy.com/mcp/servers/io-github-zleventer-google-ads-mcp)

Add the badge to your README. It turns green while your server passes our daily check. Listing details come from the official MCP registry; update them there.

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.