mcp-google-ads MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

GAQL passthrough — full query power, not just pre-baked reports
OAuth (for individuals) or Service Account (for automation)
Campaign, ad group, ad, and keyword metrics
Impressions, clicks, conversions, cost, CTR, avg CPC
Python 3.11+; .env-based config

Live-Demo

In der Praxis

google-ads.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "google-ads",
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "google-ads": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-google-ads"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add google-ads -- uvx mcp-google-ads

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: mcp-google-ads

Weekly campaign health check across accounts

👤 Paid marketing managers, agencies ⏱ ~20 min intermediate

Wann einsetzen: Weekly — which campaigns are burning budget with poor CTR / high CPA?

Voraussetzungen

Google Ads Developer Token (approved) — ads.google.com > Tools > API Center — 1-3 business days
OAuth client OR service account with Ads access — Google Cloud Console

Ablauf

List accounts

List all Google Ads accounts I can access.✓ Kopiert

→ MCC + child accounts
Pull performance

For each account, pull last 7 days: campaign name, cost, clicks, conversions, CPA. Flag campaigns where CPA > $100.✓ Kopiert

→ Ranked hot-spot list
Propose action

For the worst 3 campaigns, suggest: pause, lower bid, or investigate further based on the numbers.✓ Kopiert

→ Action plan

Ergebnis: Weekly hotspot review in minutes.

Fallstricke

Attribution windows differ by conversion action — Include segments.conversion_action_name and check each separately

Kombinieren mit: notion

Mine search terms for negative keywords

👤 Performance marketers ⏱ ~15 min intermediate

Wann einsetzen: Regular account hygiene — catch wasteful queries before they add up.

Ablauf

Pull search terms

GAQL: search_term_view for last 30 days, columns [search_term, campaign, cost, conversions]. Cost > $10 and conversions = 0.✓ Kopiert

→ Wasteful query list
Group and recommend

Group by recurring phrases. Suggest negative keywords to add at account or campaign level.✓ Kopiert

→ Negative list with level

Ergebnis: A tidy negative-keyword list to apply.

Fallstricke

Broad-matching negatives can block legit traffic — Use exact or phrase negatives first; broad only when very confident

Audit ad copy performance across a campaign

👤 Copywriters, PPC leads ⏱ ~15 min intermediate

Wann einsetzen: You launched 3 responsive ads and want to know which combos perform.

Ablauf

Pull ad stats

For campaign X, list all ads + their 30-day CTR + conv rate. Sort by conv rate desc.✓ Kopiert

→ Ad performance ranked
Recommend

What patterns distinguish top-performing ad copy? What should I iterate on?✓ Kopiert

→ Copy insights

Ergebnis: Data-driven creative iteration.

Fallstricke

Low-volume ads look worse than they are due to variance — Require minimum 100 impressions before comparing rates

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

google-ads + notion

Weekly marketing digest

Pull last week's Google Ads performance + biggest wins/losses; create a Notion page in 'Marketing Weekly'.✓ Kopiert

google-ads + postgres

Join Google Ads data with your DB for full-funnel view

Get conversion counts from Google Ads for campaign X. Query the DB for actual closed deals originating from that campaign.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
list_accessible_accounts		Discover the account graph	1 API call
run_gaql	customer_id, query: str	Any custom report	1 API call
campaign_performance	customer_id, date_range	Quick campaign digest	1 API call
ad_performance	customer_id, campaign_id?, date_range	Creative audit	1 API call

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: Google Ads API: generous per-day quota; rate-limited per QPS
Tokens pro Aufruf: Results depend heavily on date range and segments — cap rows
Kosten in €: API is free; you pay for ads separately
Tipp: Always include a date range in GAQL. Running without LIMITs can return 100k rows.

Sicherheit

Rechte, Secrets, Reichweite

Minimale Scopes: Read-only on the Ads accounts where possible

Credential-Speicherung: Service account JSON or OAuth refresh token — env vars or secret manager

Datenabfluss: Performance data goes to your LLM provider

Niemals gewähren: Admin on the Ads account to an agent that does more than read

Developer Token approval has tiers — test tokens have low quota. Apply for production.
Service account must be added as a user in Ads MCC with appropriate role.

Fehlerbehebung

Häufige Fehler und Lösungen

AUTHENTICATION_ERROR or PERMISSION_DENIED

Service account email not added to MCC with access, or developer_token wrong. Check ads.google.com > Access & Security.

Too many metrics for segment

GAQL has restrictions on which metrics can be combined with which segments. Query a simpler subset.

Prüfen: Read the GAQL compatibility table

Test token quota exceeded

Apply for production token; until then, test on small accounts with low query frequency.

Alternativen

mcp-google-ads vs. andere

Alternative	Wann stattdessen	Kompromiss
Google Ads UI / Editor	You only occasionally pull reports	Manual; no LLM insight
Meta Ads MCP	You also run Meta ads	Different platform; own auth

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen