Google Ads in Claude: connect your accounts and ask your first questions

To use Google Ads in Claude, connect your Google account to Fezola once, add Fezola to Claude as a custom connector, and ask questions in plain language. Five minutes, nothing to install, and it works across every ad account your Google account can reach. This guide is the step-by-step; for the full list of tools and safeguards, read Google Ads in Claude and ChatGPT.

Step 1: connect Google Ads in Fezola

1. Create a free Fezola account.
2. Open Sources, Add source, Google Ads.
3. Sign in with the Google account that has access to your ad accounts, and approve the Google Ads access.
4. Repeat with another Google account if your ad accounts are spread over several.

Fezola then lists every ad account those Google accounts reach, including the client accounts of manager accounts.

Step 2: add Fezola to Claude

In Claude: Customize, Connectors, + Add, Add custom connector, name it Fezola and paste https://api.fezola.com/mcp. Sign in with Fezola when Claude asks, and approve the access. Details, and the Team and Enterprise variant, in how to add a custom connector to Claude. In a conversation, make sure the Fezola connector is enabled.

Step 3: ask your first questions

Try these. Claude picks the right Fezola tool and, when needed, writes the Google Ads query for you:

1. "List my Google Ads accounts." A quick check that the connection works: names, currency, time zone, and which Google account each comes from.
2. "Show cost, clicks and conversions per campaign over the last 30 days, account by account." Uses the performance report across all your accounts at once.
3. "Which campaigns spent money this week without a single conversion?" A wasted-spend check from the same data.
4. "Give me keyword ideas for [your page URL] with average monthly searches and competition." Uses Keyword Planner ideas from seed keywords or a page.
5. "Show the ten keywords with the highest cost in this account over the last 30 days." For anything outside the standard report, Claude writes a read-only GAQL query (SELECT only).

Step 4: before you let Claude change anything

Writing is on by default for Google Ads, and it can spend real money. A few habits make it safe:

• Ask for a check first. Say "validate first": each writing tool has a validate-only mode where Google checks the change and applies nothing.
• Keep Claude's approval prompts on. The writing tools are marked destructive, so Claude asks before running them.
• Start new campaigns paused. The tool tells the assistant to create them paused unless you ask otherwise.
• Be careful with budgets and removal. A higher budget spends more, a shared budget changes for every campaign that uses it, and removing an item cannot be undone in Google Ads.
• Remember there is no spending cap on Fezola's side. Google bills what is spent.

An example that respects these: "Pause the campaigns that spent more than 50 without a conversion this month. Validate first and show me the list before applying."

If something does not work

• Claude does not see Google Ads. Check that the Fezola connector is enabled in the conversation, and that Google Ads shows as connected under Sources.
• An ad account is missing. The Google account you signed in with has no access to it: connect the Google account that does.
• A query is refused. Google returns an explanation; ask Claude to read it and fix the query.

Self-hosted or hosted?

Google also publishes an open-source Google Ads MCP server that you run yourself. The two are compared in Google Ads MCP server: hosted vs self-hosted. The same Fezola connector also manages OpenAI Ads and Microsoft Advertising.