The Google Ads MCP connector for Claude and ChatGPT: setup, safety, limits

An MCP connector is the link that lets an AI assistant use tools in an external system. “Hosted” means the server runs on the internet and you only add a URL; nothing is installed on your computer and updates are not your job.

Tecrube's connector exposes Meta, Microsoft, TikTok and LinkedIn ad accounts and Google tools such as Search Console and Tag Manager alongside Google Ads, all at one address. This article focuses on the Google Ads side only.

Three things are enough: a Google account with admin or standard access to your Google Ads account, a Claude or ChatGPT subscription that allows adding connectors, and a Tecrube account. Signing up for Tecrube is free, needs no card and comes with 75 credits that never expire.

No developer token, Google Cloud project, API key or terminal is required. All of that is handled on the hosted server's side.

In Claude, open Settings, go to Connectors, choose “add custom connector” and paste the URL copied from your Tecrube member panel (/app). The connector appears in the list; enable it from the tools icon in a new chat.

When the first Google Ads tool is called, Google's authorisation screen opens in the browser. You choose which ad accounts to grant; if you use an MCC, sub-accounts appear at this step too.

In ChatGPT, follow Settings → Connectors, add a new connector and paste the same URL. The address is identical; there is no separate Tecrube setup for Claude and for ChatGPT. Authorisation again happens on Google's OAuth screen.

For teams that use both assistants this matters: the account is connected once and every member sees the same tools in their own assistant. Claude Code and Cursor accept the same URL as well.

Start with reads: “list the campaigns in my account with status and daily budget”. Then “search terms that spent without converting in the last 30 days”. Then a first write attempt: “raise this campaign's daily budget from $50 to $60”. A preview arrives: campaign name, old value, new value. You say “approve”, it is applied and logged.

Those three commands show the connector's three core behaviours: instant reads, previewed writes, and a record.

Your password is never shared; Google's OAuth grant is used and can be revoked at any time from your Google account settings. Writes follow preview → approve → apply; nothing changes without approval. Single-step budget increases above fifty percent are rejected, new campaigns are created paused, and every approval is logged with who, when and what.

The limits should be stated plainly as well: the assistant can only use the tools the server defines, and not every setting in the Google Ads interface may be exposed as a tool. In that case the assistant says what it cannot do rather than making something up.

If the connector appears in the list but the tools do not show up in chat, open a new conversation and make sure the connector is enabled from the tools menu; some clients do not add a new connector to an existing chat. If the authorisation screen does not open, the browser's pop-up blocker is the first suspect.

An “account not found” error usually comes from signing in with the wrong Google account: the account with access to Google Ads and the one open in the browser can differ. Check the account choice on the OAuth screen. If you use an MCC, authorising with the manager account rather than a sub-account makes all client accounts visible at once.

None of these needs a setting on Tecrube's side; they all sit at the client or Google account level. If one persists, the connection status screen in the member panel (/app) shows which step has not completed.

You start with 75 free credits. Pro is $49 a month for a single account, Agency is $99 a month for teams managing several client accounts under an MCC, and Enterprise starts at $299 for corporate needs. Cancel with one click. The connector URL is the same on every plan; the plan only sets the credit amount and account scope.