google-ads-connector

Connect and operate Google Ads (read campaigns, ad groups, ads, keywords, search terms, audiences; pull reports for spend/conversions/ROAS; pause/resume campaigns and adjust budgets). Phase 1 captures credentials and Phase 1F wraps Google's official MCP server (github.com/googleads/google-ads-mcp) for read operations — Phase 2 reads call mcp__google_ads__search / list_accessible_customers / get_resource_metadata. Writes (pause/resume campaign, change budget) stay on direct REST because the official MCP is read-only. Each participant has their own Google Cloud OAuth client and their own developer token. Phase 0 picks between Test mode (immediate dev-token, only works with Google Ads test accounts) and Basic Access mode (live data, real customer, but Google reviews the dev-token application over ~1-3 business days). Phase 1 drives Google Cloud Console + Google Ads API Center + Google's OAuth consent flow + the optional 'New Google Ads account' wizard, all inside a Playwright MCP browser. Credentials persist at

By selrai-company schedule Updated 6/2/2026