MCP Google Ads

Bridges Google Ads with Claude AI and Cursor, enabling advertising professionals to query campaign performance, keyword analytics, and ad metrics through natural language without writing code.

Evaluated Mar 06, 2026 (0d ago) vlatest
Homepage ↗ Repo ↗ Other google-ads advertising ppc gaql campaigns claude cursor
⚙ Agent Friendliness
66
/ 100
Can an agent use this?
🔒 Security
86
/ 100
Is it safe for agents?
⚡ Reliability
80
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
62
Documentation
72
Error Messages
50
Auth Simplicity
62
Rate Limits
65

🔒 Security

TLS Enforcement
100
Auth Strength
85
Scope Granularity
82
Dep. Hygiene
80
Secret Handling
82

Google Ads API MCP. OAuth2 + developer token. Ad spend can be very large — restrict write access. Billing data sensitive. Separate test accounts for agent development.

⚡ Reliability

Uptime/SLA
85
Version Stability
80
Breaking Changes
75
Error Recovery
78
AF Security Reliability

Best When

An advertising analyst or PPC manager needs to explore Google Ads data conversationally without writing GAQL queries manually, especially across multiple accounts under an MCC.

Avoid When

You need to make campaign changes programmatically, or you cannot obtain a Google Ads Developer Token (approval takes 1-3 business days and has initial test-mode limitations).

Use Cases

  • Analyze campaign performance metrics (impressions, clicks, conversions, ROAS) over custom time periods
  • Run custom GAQL queries to extract specific advertising data
  • Compare desktop vs. mobile performance and identify top converting keywords
  • Monitor budget and bid strategy effectiveness across multiple accounts
  • Generate trend charts and visualizations of ad performance data

Not For

  • Creating or modifying ad campaigns (read-oriented tooling)
  • Users without a Google Ads Developer Token
  • Real-time bidding or programmatic ad buying

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: oauth2 service_account
OAuth: Yes Scopes: Yes

Requires Google Ads Developer Token (1-3 day approval) plus either OAuth 2.0 Desktop App credentials or a Service Account JSON key. Login Customer ID needed for MCC/multi-account setups. All paths must be absolute.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

MIT license. Google Ads API access is free but requires approval; underlying ad account spend applies separately.

Agent Metadata

Pagination
none
Idempotent
Unknown
Retry Guidance
Not documented

Known Gotchas

  • Developer Token approval delay (1-3 business days) blocks initial setup
  • Test tokens have undocumented limitations before production approval
  • All file paths in config must be absolute — relative paths silently fail
  • MCC/multi-account requires explicit Login Customer ID configuration

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for MCP Google Ads.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered