Google Ads inside Claude chat: no code, no terminal, one connector URL

Search for “connect Google Ads to Claude” and you land on Google Cloud console screens, API access applications, developer tokens and a local server you run from a terminal. That path exists, but it is far too heavy for a business owner who just wants to manage ads.

A hosted connector absorbs all of those steps for you. Tecrube exposes a single connector URL for Google Ads; you paste it into Claude's custom connector setting, sign in with Google and start chatting. Nothing is installed on your machine.

Step one: in Claude, open Settings, go to Connectors, add a custom connector and paste the URL from your Tecrube member panel (/app). Step two: on the first tool call Google's authorisation screen opens in the browser and you choose which ad accounts to grant. Your password never passes through Tecrube.

Step three: chat. Start with something like “summarise campaign performance for this month”. The answer is read from the live account, so the figures are real, not estimated. From setup to first answer usually takes a few minutes.

On the read side there are reports, search term analysis, quality score breakdowns and change history. Ask for “search terms that spent more than $20 in the last fourteen days without a conversion” and you get a table, with the model commenting on why each row may be irrelevant.

On the write side: adding negative keywords, changing budgets, pausing campaigns, creating campaigns and ad groups, writing responsive search ads and editing conversion goals. All of it happens in the same chat without opening a separate dashboard.

Tecrube works on a preview → approve → apply sequence. Every write request first returns a server-side preview: which campaign, which field, old value and new value. Until you say “approve”, nothing is written to the account.

Two more guardrails sit on top: a single-step budget increase above fifty percent is rejected, and new campaigns are created paused. Every approved change is logged with who, when and what, and you can review it from the panel later.

Three profiles stand out. First, the business owner who runs their own ads but gets lost in the interface: once the weekly routine moves into chat, the dashboard is opened only for exceptions. Second, the freelancer or small agency looking after several client accounts: they move between accounts under an MCC by saying “switch to this client”, and each account's changes are approved and logged separately.

Third, the marketing team member who does not know Google Ads inside out but needs reports and small edits: instructions like “pause this campaign” or “raise that budget” require no interface knowledge, and the preview removes the fear of making a mistake.

The one scenario it does not fit is a team that wants no changes made to the account and only needs to read data; for them Google's official server may be enough. The next section explains that difference.

Google's own Google Ads MCP server is read-only by design: it will not pause a campaign, move a budget or change a bid, and you need your own Cloud project to set it up. If reading data is all you want, it is a fine option.

Tecrube is a hosted server that combines reads with approved writes, and the same connector also covers Meta, Microsoft, TikTok and LinkedIn ads next to Google Ads. Which one fits you depends on whether you want to change anything in the account.

After sign-up you get 75 free credits that never expire. Pro is $49 a month for a single account, Agency is $99 a month for teams with several accounts, and Enterprise starts at $299 for corporate needs. The same connector URL also works in ChatGPT, Claude Code and Cursor; connect once and use whichever assistant you prefer.