/ Annuaire / Playground / mcp-google-ads
● Officiel cohnen ⚡ Instantané

mcp-google-ads

par cohnen · cohnen/mcp-google-ads

Run GAQL against your Google Ads account from chat — account listing, campaign + ad performance, custom queries — with OAuth or service-account auth.

mcp-google-ads is a Python MCP that talks to the Google Ads API. Five capabilities: list accessible accounts, run arbitrary GAQL, read campaign performance, read ad performance, and run custom queries. Requires a Google Ads Developer Token (1-3 business day approval) and either OAuth or service account auth.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

google-ads.replay ▶ prêt
0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "google-ads": {
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "google-ads",
      "command": "uvx",
      "args": [
        "mcp-google-ads"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json
{
  "context_servers": {
    "google-ads": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-google-ads"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcp-google-ads

Weekly campaign health check across accounts

👤 Paid marketing managers, agencies ⏱ ~20 min intermediate

Quand l'utiliser : Weekly — which campaigns are burning budget with poor CTR / high CPA?

Prérequis
  • 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
Déroulement
  1. List accounts
    List all Google Ads accounts I can access.✓ Copié
    → MCC + child accounts
  2. Pull performance
    For each account, pull last 7 days: campaign name, cost, clicks, conversions, CPA. Flag campaigns where CPA > $100.✓ Copié
    → Ranked hot-spot list
  3. Propose action
    For the worst 3 campaigns, suggest: pause, lower bid, or investigate further based on the numbers.✓ Copié
    → Action plan

Résultat : Weekly hotspot review in minutes.

Pièges
  • Attribution windows differ by conversion action — Include segments.conversion_action_name and check each separately
Combiner avec : notion

Mine search terms for negative keywords

👤 Performance marketers ⏱ ~15 min intermediate

Quand l'utiliser : Regular account hygiene — catch wasteful queries before they add up.

Déroulement
  1. Pull search terms
    GAQL: search_term_view for last 30 days, columns [search_term, campaign, cost, conversions]. Cost > $10 and conversions = 0.✓ Copié
    → Wasteful query list
  2. Group and recommend
    Group by recurring phrases. Suggest negative keywords to add at account or campaign level.✓ Copié
    → Negative list with level

Résultat : A tidy negative-keyword list to apply.

Pièges
  • 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

Quand l'utiliser : You launched 3 responsive ads and want to know which combos perform.

Déroulement
  1. Pull ad stats
    For campaign X, list all ads + their 30-day CTR + conv rate. Sort by conv rate desc.✓ Copié
    → Ad performance ranked
  2. Recommend
    What patterns distinguish top-performing ad copy? What should I iterate on?✓ Copié
    → Copy insights

Résultat : Data-driven creative iteration.

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

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

google-ads + notion

Weekly marketing digest

Pull last week's Google Ads performance + biggest wins/losses; create a Notion page in 'Marketing Weekly'.✓ Copié
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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
Google Ads API: generous per-day quota; rate-limited per QPS
Tokens par appel
Results depend heavily on date range and segments — cap rows
Monétaire
API is free; you pay for ads separately
Astuce
Always include a date range in GAQL. Running without LIMITs can return 100k rows.

Sécurité

Permissions, secrets, portée

Portées minimales : Read-only on the Ads accounts where possible
Stockage des identifiants : Service account JSON or OAuth refresh token — env vars or secret manager
Sortie de données : Performance data goes to your LLM provider
Ne jamais accorder : Admin on the Ads account to an agent that does more than read

Dépannage

Erreurs courantes et correctifs

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.

Vérifier : Read the GAQL compatibility table
Test token quota exceeded

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

Alternatives

mcp-google-ads vs autres

AlternativeQuand l'utiliserCompromis
Google Ads UI / EditorYou only occasionally pull reportsManual; no LLM insight
Meta Ads MCPYou also run Meta adsDifferent platform; own auth

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills