Can it change campaigns?

Not in the current release — it is read-only, focused on account discovery and performance reporting. Bid, budget, and asset changes must go through the UI or API with human approval.

What credentials do I need?

A Google Ads developer token, a Google Cloud project, and OAuth client credentials (or a service account via application default credentials).

Via pipx: `pipx run --spec git+https://github.com/googleads/google-ads-mcp.git google-ads-mcp`. It speaks stdio; Cloud Run deployment adds HTTP access.

Google Ads

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Query Google Ads campaigns, metrics, and account performance with GAQL — Google's official MCP.

Score 64(?)GoogleApache-2.0Verified Jul 16, 2026Top MCPs for Marketing & SEO →

Install View on GitHub

Quick answer

What it does

Exposes the Google Ads API as MCP tools: list_accessible_customers, search (GAQL for metrics/budgets/status), and get_resource_metadata for field structures.

Best for

Google Ads performance reporting
GAQL queries for metrics and budgets
Account discovery (accessible customers)
Read-only, safe-by-default ad analysis

Not for

Changing bids, budgets, or creatives (read-only today)
Non-Google ad platforms

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleads/google-ads-mcp.git",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export GOOGLE_PROJECT_ID=your_gcp_project
# export GOOGLE_ADS_DEVELOPER_TOKEN=your_22_char_token
claude mcp add google-ads -- pipx run --spec git+https://github.com/googleads/google-ads-mcp.git google-ads-mcp

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleads/google-ads-mcp.git",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleads/google-ads-mcp.git",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleads/google-ads-mcp.git",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "google-ads": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleads/google-ads-mcp.git",
        "google-ads-mcp"
      ],
      "env": {
        "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "pipx",
          "args": [
            "run",
            "--spec",
            "git+https://github.com/googleads/google-ads-mcp.git",
            "google-ads-mcp"
          ],
          "env": {
            "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
            "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.google-ads]
command = "pipx"
args = [
  "run",
  "--spec",
  "git+https://github.com/googleads/google-ads-mcp.git",
  "google-ads-mcp",
]
env = { GOOGLE_PROJECT_ID = "${GOOGLE_PROJECT_ID}", GOOGLE_ADS_DEVELOPER_TOKEN = "${GOOGLE_ADS_DEVELOPER_TOKEN}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "google-ads": {
      "command": {
        "path": "pipx",
        "args": [
          "run",
          "--spec",
          "git+https://github.com/googleads/google-ads-mcp.git",
          "google-ads-mcp"
        ]
      },
      "env": {
        "GOOGLE_PROJECT_ID": "${GOOGLE_PROJECT_ID}",
        "GOOGLE_ADS_DEVELOPER_TOKEN": "${GOOGLE_ADS_DEVELOPER_TOKEN}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Google Ads doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set GOOGLE_PROJECT_ID, GOOGLE_ADS_DEVELOPER_TOKEN in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. marketing & seo work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-marketing-seo

Compare Google Ads against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Google Ads MCP vs [Google Analytics MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/google-ads
- top-mcps.com listing for Google Analytics

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Google Ads MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/google-ads (fetch https://top-mcps.com/mcp/google-ads.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (GOOGLE_PROJECT_ID, GOOGLE_ADS_DEVELOPER_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

Jul 16, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Nov 1, 2025
Initial directory listing.

More Marketing & SEO MCPs

Other tools in the same category worth evaluating.

DataForSEO

Official

Live SERP, keyword, backlink, and on-page SEO data for an AI agent.

seoserpkeywordsbacklinks

10 minMedium

Google Analytics

Official

Query GA4 reports, funnels, and realtime data from an AI agent.

analyticsga4google-analyticsreporting

15 minMedium

Google Search Console

Query Search Console clicks, impressions, and queries from an AI agent.

seosearch-consolegscorganic-search

15 minMedium

Compared with Google Ads

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Google AdsvsGoogle Analytics Google AdsvsDataForSEO Google AdsvsSemrush Google AdsvsAhrefs

Exploring Top MCPs for Marketing & SEO? See all Marketing & SEO MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Agent prompt pack

Full details

Frequently asked questions

Can it change campaigns?

What credentials do I need?

How do I run it?

What changed

More Marketing & SEO MCPs

DataForSEO

Google Analytics

Google Search Console

Compared with Google Ads