Connect Claude to Google Ads

Inspect campaigns, ad groups, keywords, and performance. Toolspoke puts 14 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: OAuth 2.0
Actions exposed: 14
Cost per call (typical): 1 credit
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Google Ads
Open the marketplace in your workspace, add Google Ads to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with oauth 2.0. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Google Ads shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Google Ads asks for

OAuth 2.0. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

OAuth client IDRequired: Google Cloud console → APIs & Services → Credentials → OAuth 2.0 Client IDs (Desktop app).; 123-abc.apps.googleusercontent.com
OAuth client secretRequired: Shown next to the OAuth client ID in the Google Cloud console.
OAuth refresh tokenRequired: Generate once with the https://www.googleapis.com/auth/adwords scope and offline access, then paste it here.
Developer tokenRequired: Google Ads UI → Tools → API Center, on the manager account. Required on every API call.; 22-character token
Manager (MCC) customer IDOptional: Sent as login-customer-id. Required when the OAuth user reaches the account through a manager account.
Default customer IDOptional: Used whenever an action is called without an explicit customer_id.

What Claude can do in Google Ads

14 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 14Reads
Writes: 0Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

list_accessible_customers
List every Google Ads account the connected OAuth user can reach. Call this first when you do not know which customer ID to work with; manager accounts are included, so follow up with list_child_accounts to reach the accounts that actually hold campaigns.
list_child_accounts
List the accounts sitting under a manager (MCC) account, including nested levels. Use it to turn a manager customer ID from list_accessible_customers into the client customer IDs that hold campaigns and spend.
account_performance
Return account-level spend and performance totals (impressions, clicks, CTR, cost, conversions) for one customer over a date range. Set segment_by_date to get a day-by-day series instead of a single total. Cost values are micros: divide by 1,000,000 for the account currency.
account_performance_daily
Account spend and performance broken down by day. Use account_performance for a single total over the range. Cost values are micros: divide by 1,000,000.
list_campaigns
List campaigns in an account with their structure - status, channel type, bidding strategy, flight dates and daily budget. Returns campaigns regardless of whether they have recent traffic; use campaign_metrics when you need performance numbers.
campaign_metrics
Return per-campaign performance for a date range, sorted by spend. Use this for 'which campaigns are spending / converting' questions. Campaigns with no delivery in the window are omitted. Cost fields are micros (divide by 1,000,000).
campaign_metrics_daily
Campaign performance broken down by day. Use campaign_metrics for one row per campaign over the range. Cost values are micros: divide by 1,000,000.
list_ad_groups
List ad groups with their campaign, status, type and CPC bid, optionally scoped to one campaign. Use it to drill from a campaign into the ad groups that hold keywords and ads.
search_keywords
Find keywords in an account by text, ad group or campaign, returning match type, status, bid and whether the keyword is a negative. This is structural - it lists keywords even if they had no traffic. Use keyword_metrics for performance.
keyword_metrics
Return keyword-level performance (impressions, clicks, CTR, cost, conversions) for a date range, sorted by spend. Use it to find the keywords driving or wasting budget. Cost fields are micros.
search_terms_report
Return the actual user queries that triggered ads over a date range, with the keyword that matched and the resulting cost and conversions. Use it to spot irrelevant traffic worth adding as negative keywords, or new queries worth targeting.
list_ads
List the ads in an account or ad group with their type, status, final URLs and responsive search ad headlines and descriptions. Use it to review live ad copy before recommending changes.
list_campaign_budgets
List the budgets configured in an account with their amount, delivery method and Google's recommended amount, plus which campaigns share each one. Read-only: this adapter never changes a budget.
run_gaql_query
Run an arbitrary read-only Google Ads Query Language (GAQL) statement, for reports the dedicated actions do not cover - geo, device, audience, asset, conversion_action, change_event and so on. The query must start with SELECT; a LIMIT is appended when you omit one. Prefer the dedicated actions when they fit.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 14 actions above are the whole of it. A call to any other name is refused before it reaches Google Ads rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It only reads: Every action here reads. Nothing this connector can do changes anything in Google Ads.
It reaches no further than your credential: Toolspoke holds no access to Google Ads of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Google Ads: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Google Ads. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Google Ads's own rate limits. A call that Google Ads refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Google Ads?

14 named actions: 14 that only read. They include list_accessible_customers, list_child_accounts and account_performance. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Google Ads connector need?

OAuth 2.0. The connector asks for oauth client id, oauth client secret, oauth refresh token and developer token, and optionally manager (mcc) customer id and default customer id. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Google Ads connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 14 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Google Ads connector not do?

The 14 actions above are the whole of it. A call to any other name is refused before it reaches Google Ads rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Every action here reads. Nothing this connector can do changes anything in Google Ads. Toolspoke holds no access to Google Ads of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Google Ads. An agent has to ask. Toolspoke does not retry, queue or back off around Google Ads's own rate limits. A call that Google Ads refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Google Ads's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Google Ads?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More marketing connectors

Browse all of them