How to connect Google Ads to ChatGPT: nine steps with developer mode and OAuth
Enable developer mode in ChatGPT, paste the MCP server address, sign in with Google. Your password stays private, and the same setup also covers Claude.
Tecrube team
Marketing automation
The most common roadblocks in Google Ads management
Three complaints repeat: no time to read the search terms report, nobody notices which campaign is capped by budget, and every change means opening the dashboard. The shared cause is that the data does not live somewhere that talks to you.
Connected to ChatGPT, the account comes into a chat: you ask, the answer comes from live data; if you want a change, you see a preview and approve it.
What changes once it is connected
“List search terms from the last 30 days that spent over $20 without a conversion” is answered in seconds. When you say “add these as negatives”, Tecrube produces a preview; you approve and it is applied. Building reports, comparing budgets and reading change history are reads that spend no credits.
The change is that time spent in the dashboard gives way to questions. A car rental company, for example, asks at the start of the week “which city brought last week's most expensive conversions?”, updates location bids through a preview based on the answer, and is done in five minutes.
Setup, step by step
1. Open a free Tecrube account; your connector address is shown in the /app panel. 2. In ChatGPT, go to Settings → Connectors. 3. Enable developer mode at the bottom of the page. 4. Add a new connector with “Create” and name it Tecrube. 5. Paste the address copied from the panel into the server URL field.
6. Choose OAuth for authentication and save. 7. Open a new chat and enable the connector in it. 8. Type “connect my Google Ads account”; Google's sign-in window opens, grant access. 9. Ask your first question: “which of my campaigns were limited by budget this week?” Setup is available in the web interface on paid ChatGPT plans only.
Should the “elevated risk” notice worry you?
ChatGPT shows a standard notice for every custom connector with write access; it concerns the type, not the connector itself. In Tecrube, writes pass through an approval gate on the server: nothing is applied without a preview, budget increases above fifty percent are rejected and every change is written to the audit log.
You never type your password into ChatGPT; access is granted in Google's OAuth window and revoked from the panel in one click. Your account data returns only to your chat and is sent nowhere else.
The same setup covers Claude
The connector address is not specific to ChatGPT. You can add the same address in Claude under Settings → Connectors, in Claude Code with the claude mcp add command and in Cursor in the mcp.json file. Because the Google authorisation is tied to your Tecrube account, it is done once.
Connecting several Google Ads accounts is limited to one account per platform on Pro; every client account under an MCC requires the Agency plan.
Plan options, in short
Free: 75 credits that never expire, no card. Pro: $49 a month, 5,000 credits, all campaign types. Agency: $99 a month, unlimited credits, MCC. Enterprise: from $299, per seat. You can remove the connection from the panel at any time.
In short: enable developer mode, paste the address, sign in with Google. No code, no API key; ten minutes to your first question.
Common setup problems
If developer mode does not appear in the Connectors menu, your account is probably on a free plan or you are looking in the mobile app; setup works only in the web interface on paid plans. On business accounts an administrator may have switched the option off, in which case you need permission from your workspace admin.
If the OAuth window opens and immediately closes, check the browser's pop-up blocker. If you signed in with Google but the ad account does not show, the Google account you used may lack access to it; check the ad account's authorised users. Asking “list my Google Ads accounts” shows directly which accounts are visible.
If the chat seems not to use the connector's tools, make sure the connector is enabled in that chat; you may need to switch it on separately in each new conversation.
If none of these is the cause, removing the connection from the panel and adding it again solves most cases; it changes nothing in your ad account and does not erase your audit log. If the problem persists, send what you tried and the error message to the support team; on Pro and above, priority support comes from a human. The whole setup rarely takes more than ten minutes.