Google Ads Mcp

io.github.davidmosiahPublished by GitHub account davidmosiahv0.1.3Updated Oct 24, 2026

Unofficial Google Ads MCP for campaigns, keywords, budgets, and gated mutations.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Unofficial local MCP server that lets an assistant read and analyze a Google Ads account and, when explicitly enabled, pause or resume campaigns and keywords,

What you can do
Inspect accounts, campaigns, ad groups, keywords and performance metrics, plus connection status, capabilities and privacy audits through diagnostic tools. Run workflow helpers such as a daily performance report and a read-only waste finder that ranks keywords with spend and no conversions. Manage the shared Delx profile and onboarding. Handle OAuth: get an auth URL, exchange a code, revoke access. When mutations are enabled, pause or resume keywords and campaigns, set keyword bids and set campaign budgets.
When to use it
Useful when you want an assistant to answer questions about Google Ads performance, produce daily or waste reports, or make small, reviewed account changes such as pausing a keyword or adjusting a budget without leaving the chat client.
Requirements
Runs locally via npx (Node.js) over stdio, with an optional loopback-only HTTP mode. Needs a Google Ads developer token and a Google OAuth client ID and secret, plus a one-time setup wizard and OAuth consent. A manager (MCC) customer ID is needed for multi-account access. Network access to the Google Ads API.
Before you install
Unofficial and not affiliated with Google. Write tools are off by default; enabling GOOGLE_ADS_ALLOW_MUTATIONS lets the assistant change real ad spend, bids, budgets and campaign status, and each mutation also requires explicit user intent. Review every proposed change. The developer token and client secret are stored in a local config file, and OAuth tokens in a local token file. Raw privacy mode returns full customer IDs and payloads.

Installation

In SourceWeft

  1. Open Google Ads Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

google-ads-mcp-unofficial

[CI] [npm] [npm downloads] [MIT] [MCP]

Unofficial Model Context Protocol server that lets AI agents read, analyze, and (gated) act on a Google Ads account — pause keywords, set bids, adjust budgets — without leaving your stack.

Unofficial. Not affiliated with Google. This is a local-first MCP server that speaks the Google Ads REST API directly. It does NOT include automated financial-account changes beyond what the Google Ads API allows. Always review proposed changes before enabling GOOGLE_ADS_ALLOW_MUTATIONS.


HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

bash
npx -y google-ads-mcp-unofficial --http# GET  http://127.0.0.1:3000/health# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: GOOGLE_ADS_MCP_HOST, GOOGLE_ADS_MCP_PORT, GOOGLE_ADS_MCP_TRANSPORT=http.

Quick start (30 seconds)

bash
npx -y google-ads-mcp-unofficial setup

The setup wizard collects your developer token + OAuth client, writes ~/.google-ads-mcp/config.json (chmod 600), then walks you through the OAuth dance via a local callback at http://127.0.0.1:3000/callback.

Verify:

bash
npx -y google-ads-mcp-unofficial doctor

Then add it to your agent (Claude Desktop, Cursor, Hermes, OpenClaw, Codex — see examples below).


What it does

22 tools across 6 categories.

CategoryCountExamples
Meta / diagnostic5google_ads_connection_status, google_ads_capabilities, google_ads_agent_manifest, google_ads_data_inventory, google_ads_privacy_audit
Shared Delx profile3google_ads_profile_get, google_ads_profile_update, google_ads_onboarding
Auth3google_ads_get_auth_url, google_ads_exchange_code, google_ads_revoke_access
Reads (always safe)8google_ads_list_accounts, google_ads_list_campaigns, google_ads_get_campaign, google_ads_list_ad_groups, google_ads_list_keywords, google_ads_get_account_performance, google_ads_get_campaign_performance, google_ads_get_keyword_performance
Workflow2google_ads_daily_report, google_ads_find_waste
Mutations (gated)6google_ads_pause_keyword, google_ads_resume_keyword, google_ads_set_keyword_bid_micros, google_ads_set_campaign_budget_micros, google_ads_pause_campaign, google_ads_resume_campaign

Full tool reference: see AGENTS.md.


Setup wizard

bash
npx -y google-ads-mcp-unofficial setup [--allow-mutations] [--client hermes|claude|cursor|...]

What it does:

  1. Prompts for: developer token, OAuth client id/secret, optional login_customer_id (MCC), redirect URI, privacy mode.
  2. Writes ~/.google-ads-mcp/config.json with chmod 600.
  3. Writes an MCP client config (e.g. merges into claude_desktop_config.json on macOS; writes a Hermes block and skill file for --client hermes).
  4. Runs the OAuth dance (unless --no-auth) by opening Google's consent screen and listening on 127.0.0.1:3000.

Mutations are off by default. --allow-mutations enables write tools. ASK THE USER before turning this on — it lets agents change campaigns, bids, budgets, and pause/resume keywords.


Auth model

This MCP requires two credentials:

  1. Google Ads Developer Token — from your MCC (Manager) account at https://ads.google.com/aw/apicenter. New tokens start in "Test account access" mode and need approval for production traffic.
  2. Google OAuth 2.0 Client — a "Desktop" or "Web" client created in Google Cloud Console. The single OAuth scope used is https://www.googleapis.com/auth/adwords.

⚠️ Refresh token gotcha: Google only returns a refresh_token on first consent or after you revoke the prior grant at https://myaccount.google.com/permissions. Our auth flow uses prompt=consent to maximize the chance Google returns one — but if your code-exchange response is missing refresh_token, the tool will tell you to revoke and retry.

VariablePurposeStored whereSecret?
GOOGLE_ADS_DEVELOPER_TOKENApproved developer token~/.google-ads-mcp/config.json or envyes
GOOGLE_ADS_CLIENT_IDOAuth client idlocal or envno
GOOGLE_ADS_CLIENT_SECRETOAuth client secretlocal or envyes
GOOGLE_ADS_LOGIN_CUSTOMER_IDMCC id (no dashes)local or envno
GOOGLE_ADS_REDIRECT_URIOAuth callbacklocal or env (default http://127.0.0.1:3000/callback)no
GOOGLE_ADS_PRIVACY_MODEsummary | structured | rawlocal or env (default structured)no
GOOGLE_ADS_ALLOW_MUTATIONSEnable write toolslocal or env (default false)no
GOOGLE_ADS_TOKEN_PATHOverride token storagelocal or env (default ~/.google-ads-mcp/tokens.json)no
GOOGLE_ADS_CACHEEnable SQLite cachelocal or env (default off)no
GOOGLE_ADS_CACHE_PATHOverride cache pathlocal or envno
GOOGLE_ADS_NO_RETRYDisable retry middlewareenv (default off)no

Privacy modes

ModeWhat you getCustomer id
summaryid + name + status fields onlypartial-redacted (123-***-7890)
structured (default)flat normalized rows with metricspartial-redacted
rawfull upstream Google Ads REST payloadfull

Pass privacy_mode per call to override the default per response.

Redaction matrix:

Fieldsummarystructuredraw
developer_tokenn/an/an/a (never returned)
access_token, refresh_token, client_secret[REDACTED] in all errors[REDACTED][REDACTED]
email addresses in error messages[REDACTED][REDACTED][REDACTED]
customer_id123-***-7890123-***-7890full
metrics (clicks, cost, etc.)droppedincludedincluded

⚠️ Mutation gating — read this

Default: mutations are DISABLED. Six tools are gated:

  • google_ads_pause_keyword / google_ads_resume_keyword
  • google_ads_set_keyword_bid_micros
  • google_ads_set_campaign_budget_micros
  • google_ads_pause_campaign / google_ads_resume_campaign

If an agent calls any of them without GOOGLE_ADS_ALLOW_MUTATIONS enabled, it gets:

Error: Write tools are disabled. To enable: re-run `google-ads-mcp-server setup --allow-mutations`or enable GOOGLE_ADS_ALLOW_MUTATIONS. ASK THE USER BEFORE TURNING THIS ON — it lets agentschange campaigns, bids, budgets, and pause/resume keywords.

Even with the env enabled, every mutation requires explicit_user_intent: true in the per-call arguments. And every mutation is logged to stderr with the resource name:

[google-ads-mcp] MUTATION pause_keyword {"resource_name":"customers/1234567890/adGroupCriteria/999~111222333"}

Read SECURITY.md for the threat model.


Agent client examples

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

json
{  "mcpServers": {    "google-ads": {      "command": "npx",      "args": ["-y", "google-ads-mcp-unofficial"]    }  }}

Then restart Claude Desktop.

Cursor / Windsurf

~/.cursor/mcp.json (or your IDE equivalent):

json
{  "mcpServers": {    "google-ads": {      "command": "npx",      "args": ["-y", "[email protected]"]    }  }}

Hermes

yaml
# ~/.hermes/config.yamlmcp_servers:  google-ads:    command: npx    args:      - -y      - [email protected]    timeout: 120    connect_timeout: 60    sampling:      enabled: false

Then /reload-mcp (do NOT restart the gateway for normal data access).

OpenClaw

~/.openclaw/mcp.servers.json:

json
{  "google-ads": {    "command": "npx",    "args": ["-y", "[email protected]"]  }}

Codex / TOML clients

See examples/codex.toml for the equivalent TOML block.


Workflow examples

1. Daily performance pulse

jsonc
// Agent asks: "How did my Google Ads do yesterday?"{  "name": "google_ads_daily_report",  "arguments": {    "customer_id": "1234567890",    "cpc_alert_threshold": 0.15  }}

Returns markdown with yesterday + 7d + 30d aggregates. If yesterday's CPC exceeds 0.15, the output gets an ALERT banner.

2. Identify waste (read-only)

jsonc
{  "name": "google_ads_find_waste",  "arguments": {    "customer_id": "1234567890",    "date_range": "LAST_30_DAYS",    "min_clicks": 5,    "min_cost_micros": 200000,    "zero_conversions_only": true  }}

Returns a ranked list of keywords matching "spent ≥ $0.20 with ≥5 clicks and 0 conversions" — but never pauses them.

3. Pause a single keyword (mutation, gated)

After the user confirms:

jsonc
{  "name": "google_ads_pause_keyword",  "arguments": {    "customer_id": "1234567890",    "ad_group_id": "999",    "criterion_id": "111222333",    "explicit_user_intent": true  }}

Troubleshooting

SymptomAction
Missing required Google Ads environment variablesRun setup or set the env vars listed in the error.
Google did not return a refresh_tokenRevoke at https://myaccount.google.com/permissions then re-run auth.
PERMISSION_DENIED on a readConfirm GOOGLE_ADS_LOGIN_CUSTOMER_ID matches the MCC that owns the target customer (no dashes).
Write tools are disabledExpected. Ask the user before enabling GOOGLE_ADS_ALLOW_MUTATIONS.
Hermes tools missing after config edit/reload-mcp or hermes mcp test google-ads. Do NOT restart the gateway.
Token file insecure perms warningchmod 600 ~/.google-ads-mcp/tokens.json

Support


Disclaimer

Unofficial integration. Not affiliated with Google. This MCP does not include automated financial-account changes beyond what the Google Ads REST API allows. Always review proposed changes before enabling GOOGLE_ADS_ALLOW_MUTATIONS. The author is not responsible for budget overruns, paused campaigns, or any other consequences of automated changes to your Google Ads account.

MIT-licensed.

Skill or MCP

Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:

bash
npx -y google-ads-mcp-unofficial call google_ads_connection_status --json '{}'

Copy skill/SKILL.md into your agent skills dir.

Source: README.md at commit e415988

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts