mcp-google-ads
Pilot Google Ads campaigns from Claude with built-in safety guardrails
Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenInterested in sponsoring? Get in touch
An MCP server that gives Claude full read + write access to Google Ads accounts via the REST API. Every write operation goes through a two-step safety layer: draft a change, review the preview, then confirm to execute. Budget caps, bid limits, and audit logging prevent accidental spend.
git clone https://github.com/FGRibreau/mcp-google-ads.git
cd mcp-google-ads
cargo build --release
# Generate OAuth2 refresh token
./scripts/generate_token.sh ~/.mcp-google-ads/credentials.json
Add to ~/.claude/settings.json:
{
"mcpServers": {
"google-ads": {
"command": "/path/to/mcp-google-ads/target/release/mcp-google-ads",
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "your-developer-token",
"GOOGLE_ADS_CUSTOMER_ID": "123-456-7890",
"GOOGLE_ADS_CREDENTIALS_PATH": "~/.mcp-google-ads/credentials.json",
"GOOGLE_ADS_TOKEN_PATH": "~/.mcp-google-ads/token.json"
}
}
}
}
All configuration is via environment variables. No config files.
All write tools return a preview. Call confirm_and_apply with dry_run=false to execute.
~/.mcp-google-ads/credentials.json./scripts/generate_token.sh
v0.3.0 introduces breaking changes that strengthen the safety surface and
unlock zero-UI workflows for agents. Most callers only need to add a
status: None field to their existing draft structs.
If you only invoke MCP tools through Claude / an MCP host, no migration needed — the new params are all optional. You can now:
status: "ENABLED" when calling draft_campaign /
draft_responsive_search_ad / create_ad_group to start the entity
serving immediately. Default remains PAUSED.bypass_require_dry_run: true to confirm_and_apply when you
intentionally want to skip the dry-run guard (one-shot override).confirmed_twice: true to confirm_and_apply for destructive
plans flagged requires_double_confirm.exempt_policy_violations: true to confirm_and_apply to request a
Google ad policy exemption when a mutate is blocked by an exemptible
violation. Required in practice for medical/health keywords, which trip
HEALTH_IN_PERSONALIZED_ADS (and, for contraception terms, BIRTH_CONTROL).
Only keywords can be exempted — responsive search ads cannot.status_after_apply and next_action_hint from any draft / apply
response to know whether a follow-up enable_entity call is needed.// v0.2.x
DraftRsaParams { config, customer_id, ad_group_id, headlines, descriptions,
final_url, path1, path2 }
// v0.3.0
DraftRsaParams { config, customer_id, ad_group_id, headlines, descriptions,
final_url, path1, path2, status: None }
// ^^^^^^^^^^^^^ new field
// v0.2.x
DraftCampaignParams { ..., geo_target_ids, language_ids }
// v0.3.0
DraftCampaignParams { ..., geo_target_ids, language_ids, status: None }
// v0.2.x — defaulted to ENABLED (the only outlier)
create_ad_group(&config, cid, campaign_id, name, bid)
// v0.3.0 — default PAUSED (consistent with other write tools)
create_ad_group(&config, cid, campaign_id, name, bid, None)
// Equivalent v0.2.x behaviour:
create_ad_group(&config, cid, campaign_id, name, bid, Some(AdStatus::Enabled))
// v0.2.x
tools::confirm::confirm_and_apply(&config, plan_id, dry_run).await
// v0.3.0
tools::confirm::confirm_and_apply(&config, ConfirmApplyInput {
plan_id: plan_id.to_string(),
dry_run,
bypass_require_dry_run: false,
confirmed_twice: false,
}).await
apply_recommendation / dismiss_recommendation now actually work.
v0.2.x routed them through googleAds:mutate and got 400.require_dry_run = true now blocks rather than just warning.create_pmax_campaign(start_paused = false) actually produces an
ENABLED campaign (v0.2.x ignored the param).See CHANGELOG.md for the full breakdown.
cargo build # Build debug
cargo build --release # Build release binary
cargo test # Unit + wiremock integration tests (no credentials needed)
cargo clippy --all-targets --all-features -- -D warnings
cargo fmt --check
The tests/integration_test.rs suite requires real Google Ads test
credentials (GOOGLE_ADS_TEST_* env vars); the rest of the test files
(13 wiremock-driven suites) run without any credentials.
MCP server for Google Ads — full campaign management with safety guardrails
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
MCP Google Ads läuft lokal über stdio.
Zuletzt geprüft: 2026-10-27. MCP server for Google Ads — full campaign management with safety guardrails