Set up over MCP
Connect and import a Google Ads account without leaving your MCP client — the one browser step is Google consent.
Almost all of setup is drivable over MCP. The only step that must happen in a browser is Google's consent screen — an OAuth consent can't be completed from an MCP client. You'll hand the human a URL for that one step.
Check the connection
What's the Google Ads connection status for this workspace?Calls gads_get_connection_status. If it's already connected, skip to discovery.
Get the connect URL (human opens it)
Give me the Google Ads connect URL.Calls gads_get_connect_url. Open the returned URL in a browser and approve the adwords scope. This is the
one step that leaves the client.
Discover and import
Discover the ad accounts I can access, then import the one named "…".Calls gads_discover_ad_accounts then gads_import_ad_account. Manager accounts are listed but not
importable — import leaf advertiser accounts. Import enqueues a 90-day backfill.
Wait for the sync
Poll the sync status until the backfill finishes.Calls gads_get_sync_status. Reads return a dataFreshness warning while history is thin — wait it out.
Set targets
Set the optimization targets: €400/day spend goal, ROAS floor 2.0, CPA band €15–€40.Calls gads_set_optimization_targets. Now the plan is grounded.
Org-level tools like discover and import are refused under a project-scoped token — use an org-scoped token to set up new accounts.