Log inSubmit server
Google Ads logo

Google Ads

Query, analyze, validate, and manage Google Ads accounts with MCC-aware MCP tools and review safeguards.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Ads

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-ads-8": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-ads"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_VALUE_HERE",
        "GOOGLE_ADS_CLIENT_ID": "YOUR_VALUE_HERE",
        "GOOGLE_ADS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "GOOGLE_ADS_REFRESH_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

google-ads connects AI clients to the Google Ads API, including manager accounts and multiple client accounts. It detects the active client from the working directory, then exposes tools for campaign discovery, reporting, keyword research, search-term analysis, diagnostics, experiments, and GAQL queries. New changes are read-only by default or created paused, with explicit configuration required before mutating tools become available. Use it for account analysis, campaign troubleshooting, and controlled Google Ads workflows.

Use cases

  • Audit campaign and keyword performance by conversion action
  • Diagnose campaigns with low spend or missing impressions
  • Inspect search queries and search-term categories
  • Validate responsive search ads before creation
  • Run custom GAQL reports across configured client accounts

Key features

  • MCC and multi-client account support
  • Working-directory account detection
  • Keyword, ad, and search-term reporting
  • Campaign diagnostics and ad-strength checks
  • RSA validation and keyword-volume estimates
  • Raw GAQL query execution

Tools21

What Google Ads lets your agent do. Expand a tool for its parameters.

Verified live~3.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

4/4 checks healthy over the last 16d

What it can do

From the 21 tools this server returned when we ran it.

Runs commands · 1Makes network requests · 2Read-only tools · 20
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age209 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · mcp-google-ads (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads835Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed21Callable tools this server registers over MCP.

How Google Ads works

What google-ads does

google-ads exposes Google Ads API operations through Model Context Protocol tools. It supports MCC configurations with several client accounts and can select the active account from the working directory. The toolset covers campaign and ad-group discovery, campaign tracking, conversion actions, keyword and ad reporting, search-term analysis, campaign diagnostics, ad-strength checks, keyword-volume estimates, experiments, and custom GAQL queries.

Reporting tools return advertising metrics such as impressions, clicks, cost, conversions, quality-score components, impression share, ad copy, final URLs, and ad-strength ratings. Conversion-focused variants break keyword, ad, or search-term performance down by conversion action. Search-term insight tools provide category-level data and can drill into individual terms.

How it works

Configure one MCC account and map named client entries to Google Ads customer IDs and workspace folders. When an MCP client invokes google_ads_get_client_context, the server reports the account associated with the current working directory and its health status. Calling that tool first helps avoid operating against the wrong client account.

The server is read-only by default. Mutating tools remain hidden unless GOOGLE_ADS_MCP_WRITE=true is set in the server environment. New items are configured to start paused, and enabling approved items requires an approval step. RSA validation can run before creation and checks headline, description, URL, path, and label requirements. Retry and timeout handling use circuit-breaker behavior, while structured logs use Pino.

Setup and configuration

Install the npm package with npm install mcp-google-ads, or clone the repository, install dependencies, and build it. The server requires a Google Ads developer token, an OAuth client ID, an OAuth client secret, and an OAuth refresh token. The Google Ads API must be enabled in the associated Google Cloud project.

Credentials can be placed in config.json or supplied through environment variables; environment variables take precedence. Configuration includes the OAuth scope, MCC customer ID, client-account mappings, workspace folders, paused-creation behavior, label prefixes, and approval requirements. The bundled refresh-token helper uses an installed-app OAuth flow with PKCE and requests the configured Google Ads scope. Keep MCP configuration files containing credentials out of source control.

Add the server as a Node-based MCP process in Claude Code settings. Claude Desktop can also load it from its platform-specific MCP configuration file.

Tools and capabilities

  • Identify the active client account and inspect account health.
  • List campaigns, ad groups, pending labeled changes, conversion actions, experiments, and experiment details.
  • Retrieve campaign tracking settings and campaign diagnostics.
  • Report on keyword, ad, search-term, and conversion-action performance.
  • Inspect search-term categories and drill into category terms.
  • Check RSA ad strength and validate RSA inputs before creation.
  • Estimate keyword volume, competition, and CPC bid ranges.
  • Run raw Google Ads Query Language statements for resources and reports not covered by dedicated tools.

Limitations and notes

GAQL queries require valid Google Ads Query Language syntax. Search-term insights operate on one campaign at a time, and drilling into insight terms requires an insight_id from the category-insights tool. The developer token is a separate credential from the OAuth scope. Enabling write access changes the available tool surface, so protect the server environment and review changes before making them live.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Ads

google-ads is an MCP server that connects AI clients to the Google Ads API through MCC-aware account context, campaign and ad-group discovery, performance reporting, search-term analysis, RSA validation, keyword-volume estimates, diagnostics, experiments, and raw GAQL query tools. It defaults to read-only operation and supports controlled changes when explicitly enabled.

Install it with `npm install mcp-google-ads`, or clone the repository and run `npm install` followed by `npm run build`. Configure Google Ads credentials in `config.json` or environment variables, then register the built Node entry point with your MCP client.

Configure the MCC customer ID and define each client account with its customer ID, name, and workspace folder in `config.json`. The server uses the working directory to identify the client context, and `google_ads_get_client_context` reports the selected account and health status.

Set `GOOGLE_ADS_MCP_WRITE=true` in the MCP server environment. Mutating tools are hidden by default and return an error if called without this flag; newly created items are paused, and enabling approved items requires an approval step.

Yes, google-ads can be added to Claude Desktop through its platform-specific MCP configuration file. It is also documented for Claude Code, where the server runs as a Node command with the built entry point as its argument.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Ads AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-ads-8?style=directory)](https://allmcps.com/mcp/google-ads-8)
HTML Embed
<a href="https://allmcps.com/mcp/google-ads-8"><img src="https://allmcps.com/api/badge/google-ads-8?style=directory" alt="Google Ads on AllMCPs" /></a>