google-ads mcp ppc paid-search automation

Complete Guide to MCP Servers for Google Ads

How to connect Google Ads to Claude via MCP servers — setup, authentication, real campaign workflows, and what you can actually automate without breaking your account.

MarketCore Labs Team

Google Ads accounts accumulate complexity fast. Hundreds of campaigns, thousands of ad groups, millions of historical data points — and most of the actionable insight is buried. MCP servers for Google Ads let you query that complexity through natural language, run optimizations through conversation, and cut the time you spend in the Google Ads UI significantly.

This is a complete guide: what MCP servers for Google Ads can do, how to set them up, the workflows worth building, and the limits you need to respect.

What Google Ads MCP Servers Actually Do

An MCP server bridges Google Ads’ API and Claude. When connected, Claude can:

  • Query campaign, ad group, keyword, and ad performance data in real time
  • Make changes to bids, budgets, status, and ad copy
  • Run GAQL (Google Ads Query Language) queries without you knowing the syntax
  • Generate reports across date ranges, comparison periods, and custom segments
  • Create and pause campaigns, ad groups, and ads

The key word is “can.” What you should automate depends heavily on your account structure and risk tolerance. More on that below.

Choosing the Right MCP Server

There are two main options in the MarketCore directory:

Google Ads MCP (community) — The community-maintained server. Broader feature coverage, faster iteration on new capabilities, well-documented. Best for most advertisers.

Google Ads MCP (official) — The officially supported version. More conservative in scope but backed by a maintenance guarantee. Useful if you need long-term API stability.

For most users starting out, the community MCP server covers more ground. Switch to the official version if you’re deploying this in an agency context where stability is critical.

Setup

Prerequisites

Step 1: Get Your Developer Token

Google Ads API access requires a developer token. Applications typically take 1–3 business days to approve. Request it from your Google Ads manager account under Tools & Settings → API Center.

Request basic access to start — it gives you 15,000 operations per day, which is more than enough for manual workflows.

Step 2: Set Up OAuth Credentials

  1. Go to Google Cloud Console and create a new project (or use an existing one)
  2. Enable the Google Ads API
  3. Create OAuth 2.0 credentials (Desktop application type)
  4. Download the client_secret.json file

Step 3: Configure Claude Desktop

Add the MCP server to your Claude Desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):

{
  "mcpServers": {
    "google-ads": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-google-ads"],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "your-developer-token",
        "GOOGLE_ADS_CLIENT_ID": "your-oauth-client-id",
        "GOOGLE_ADS_CLIENT_SECRET": "your-oauth-client-secret",
        "GOOGLE_ADS_REFRESH_TOKEN": "your-refresh-token",
        "GOOGLE_ADS_CUSTOMER_ID": "your-customer-id"
      }
    }
  }
}

Restart Claude Desktop. A hammer icon confirms the connection.

Step 4: Generate Your Refresh Token

Run the OAuth flow once to generate a refresh token. Most Google Ads MCP servers include a helper script for this. Check the README in the tool’s GitHub repository for the specific command.

Workflows Worth Building

Weekly Performance Review

The highest-ROI workflow. Instead of building a custom report in Google Ads, ask:

“Pull last week’s performance by campaign. Show impressions, clicks, CTR, average CPC, conversions, cost per conversion, and ROAS. Compare to the previous week. Flag any campaign where ROAS dropped more than 20% or cost per conversion increased more than 25%.”

Claude queries the API and returns a formatted table with the exact flags you need. Typical time savings: 20–30 minutes per week.

Search Term Analysis

Search term reports reveal what users actually search before triggering your ads — and where you’re wasting budget on irrelevant traffic.

“Pull search terms from the last 30 days that have more than 10 impressions but zero conversions and a cost above $5. Group them by theme and suggest negative keywords for each group.”

This workflow alone typically surfaces 15–40% budget leakage in active accounts.

Ad Copy Analysis

“Compare click-through rates across all active responsive search ads in my brand campaigns. Which headline combinations have the highest CTR? Are there any headlines that appear in the lowest-performing combinations across multiple ad groups?”

Bid Adjustment Recommendations

“Look at my ad schedule bid adjustments. Compare conversion rate by hour of day for the last 90 days. Which time slots have a conversion rate more than 30% below account average? Which are more than 30% above?”

Claude can generate the specific bid adjustment values you need to implement — you review and apply them manually or ask Claude to apply them directly if you’re comfortable with write operations.

Write Operations: What to Automate vs. What to Review

Google Ads MCP servers can make changes to your account. Be deliberate about what you allow.

Safe to automate directly:

  • Pausing underperforming keywords below a threshold you define
  • Adjusting ad schedules based on performance data
  • Adding negative keywords to campaigns or ad groups

Review before applying:

  • Budget changes (a misplaced decimal can drain budget fast)
  • Bid strategy switches
  • New campaign creation

Always manual:

  • Landing page changes (not in scope for Ads MCP)
  • Account-level settings
  • Audience membership rules

A good rule: start with read-only for the first two weeks. Build confidence in what Claude pulls before trusting what it pushes.

Reporting to Clients or Stakeholders

The MCP server is particularly powerful for agency use. Ask Claude to:

“Generate a client-ready summary of this month’s Google Ads performance. Include total spend, leads, cost per lead, and month-over-month comparison. Tone: concise, no jargon, focused on business outcomes not platform metrics.”

Then copy-paste into your reporting template. The underlying data is fresh from the API; the formatting takes seconds.

Common Errors and Fixes

“Developer token not approved” — You’re using a test-level token. Apply for basic access in your manager account.

“Customer ID format error” — Strip hyphens from your customer ID. 123-456-7890 should be 1234567890.

“Quota exceeded” — You’ve hit the 15,000 daily operations limit on basic access. Apply for standard access if you need more, or batch your queries.

“OAuth token expired” — Refresh tokens expire if unused for 6 months. Re-run the OAuth flow to generate a new one.

Browse the full list of paid advertising tools in the MarketCore Toolkit to find MCP servers for other ad platforms.

Get new Google Ads automation tips and tool reviews in your inbox. Join the MarketCore newsletter.

Get more guides like this

The MarketCore newsletter covers new AI marketing tools and workflows every week.

Subscribe ← All guides