Google Search Ads 360 integrationGoogle Search Ads 360

Google Search Ads 360 integration for AI agents.

Google Search Ads 360 integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Search Ads 360 tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

What your agents can do

Real Google Search Ads 360 actions, managed and audited.

Your user connects Google Search Ads 360 once; your agent can then run Search Ads 360 reporting, customer, campaign, keyword, conversion, and custom column operations — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

  1. 1

    Your user grants Google Search Ads 360 access once (OAuth) — the token lands in the vault.

  2. 2

    Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.

  3. 3

    Every routed call appends a hash-chained audit record — nothing leaves your infra.

Available tools

Google Search Ads 360 tool surface.

The following managed tool groups are exposed by this integration. Each item is surfaced as tool metadata so agents can discover safe actions and build reliable workflows.

Google Search Ads 360 tools
Run Search Ads 360 reporting, customer, campaign, keyword, conversion, and custom column operations.
FAQ

Google Search Ads 360 integration, answered

How do AI agents use Google Search Ads 360 through Open Connector?
Your user connects Google Search Ads 360 once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Search Ads 360 tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Google Search Ads 360 MCP server?
Yes. Open Connector can serve Google Search Ads 360 as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Search Ads 360 actions with credentials injected server-side.
Where do Google Search Ads 360 credentials live?
In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Google Search Ads 360 — keep the keys.

Open source, self-hostable, with Google Search Ads 360 credentials that never leave your infrastructure. Run it from source today.