
Google Ads
io.github.ZLeventerPublished by GitHub account ZLeventerv1.0.1Updated Oct 24, 2026
MCP server for Google Ads — 22 tools for spend diagnosis, impression share, and asset performance.
Overview
A local MCP server that gives an assistant read access to Google Ads data for spend diagnosis, impression share, auction insights and asset performance.
- What you can do
- List accessible accounts and account details, campaigns, ad groups and budgets with pacing and utilization figures. Review keyword performance, search terms and conversions by campaign or conversion action. Inspect responsive search ads, ad strength and per-asset performance labels, plus account and campaign assets. Examine audiences and campaign audience targeting, geo and device splits, impression share and auction insights against competitors. Run arbitrary GAQL queries as an escape hatch for custom reports.
- When to use it
- Useful for paid search teams and agencies that want to diagnose wasted spend, budget limits, weak ad assets or lost impression share conversationally instead of building dashboards. Best when the assistant needs to answer specific performance questions about a Google Ads account.
- Requirements
- Runs locally via npx or Node.js 20 or later, or as a Docker container. Needs a Google Ads developer token, OAuth 2.0 client ID and client secret from Google Cloud Console, and a refresh token with the adwords scope, supplied as environment variables. A default customer ID is required and can be overridden per call; a manager account ID is needed only for MCC access. Network access to Google Ads is required.
Installation
In SourceWeft
- Open Google Ads in the dashboard and add it to a workspace.
- 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
[npm version] [npm downloads] [glama score] [Node.js] [MCP] [License: MIT]
MCP server for Google Ads — diagnose spend efficiency, impression share, and asset performance from Claude.
22 tools across campaigns, keywords, RSAs, assets, audiences, geo/device splits, impression share, auction insights, and budget pacing — plus a raw GAQL escape hatch. Built for B2B paid search teams and agencies running real diagnosis, not just dashboard-style "list my campaigns" queries.
Why this exists
Most Google Ads MCP servers stop at "list campaigns + basic metrics." This one goes after the questions paid search teams actually ask: which RSA assets are labeled LOW so I can replace them, which keywords burn budget with zero conversions, who am I losing impression share to in auction insights, what's my mobile vs. desktop CPA gap, which campaigns are budget-limited right now. Those are the levers you pull to fix performance — and they're all first-class tools here.
Differentiated from the official googleads/google-ads-mcp: ships RSA asset performance labels, auction insights, impression share analysis, geo/device splits, audience targeting inspection, and budget pacing.
Example prompts
Once installed, ask Claude things like:
- "What's my impression share vs competitors this month? Who am I most often losing to?"
- "Show all RSA assets with LOW performance labels so I can replace them."
- "Which keywords are spending the most with zero conversions in the last 30 days?"
- "What's my mobile vs. desktop CPA difference across all campaigns?"
- "Are any campaigns budget-limited right now? Show Lost IS (Budget)."
- "List my remarketing audiences and tell me which ones are large enough to target in Search."
Demo
🎥 Walkthrough video coming soon — diagnosing wasted spend from Claude in under 60 seconds.
Features
Prerequisites
- Node.js 20+
- A Google Ads Developer Token (apply here)
- OAuth 2.0 credentials (Client ID + Secret) from Google Cloud Console
- A refresh token with
https://www.googleapis.com/auth/adwordsscope
Environment variables
Usage
Claude Desktop (claude_desktop_config.json)
Claude Code
Cursor (~/.cursor/mcp.json)
Docker
Tools reference
Build from source
License
MIT — Copyright (c) 2026 Zach Leventer
Source: README.md at commit ceaa0dc
Tools
0Version history
1- v1.0.1LatestSep 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