Connect Claude to your Google Ads account

What you need before starting

Have three things ready. The setup itself takes under a minute; what usually stretches it is signing in with the wrong Google account.

• A Claude plan that can add custom connectors (Pro, Max, Team or Enterprise), or a ChatGPT plan with developer mode available in the web interface.
• A Google account with admin or standard access to the Google Ads account you want to manage. If you work through a manager account (MCC), the Google account authorised on that MCC.
• The connector address: https://mcp.tecrube.com/mcp. It is public and contains no secret.

How the setup flows

There are two parts, completed in order. In part one Claude connects to the Tecrube server; in part two Tecrube connects to your Google Ads account. The two links are independent: Claude never sees your Google credentials, and Google never learns which assistant you use.

• Part 1 — Add the connector: open Claude's settings, add a custom connector, paste the address, approve access to Tecrube.
• Part 2 — Authorise Google Ads: ask for an account connection in the chat, sign in with Google, choose the account to manage.

First commands after setup

Start by reading. The three requests below change nothing in your account and give you a picture of its state in seconds. Any command that would change something returns a preview first and is not applied until you approve.

• “Show campaign performance for the last 30 days with spend, conversions and CPA.”
• “List search terms that spent without converting.”
• “Audit my account; rank the conversion tracking, budget and ad strength issues.”

How the approval gate works

In Tecrube every write action is gated on the server. When the assistant wants to pause a campaign, change a budget or add a negative keyword, it first shows the full change: which account, which object, current value, new value. It is applied when you approve.

Single-step budget increases above 50% are rejected. Every applied change is written to the audit log and can be listed from the chat. An “always allow this tool” setting on the Claude side does not bypass the gate; the gate lives on the Tecrube server, not in the client.

The same address in other apps

If you use an assistant other than Claude, the number of steps stays the same; only where you add the connector changes. The Google authorisation (part 2) is identical everywhere and, because it is tied to your Tecrube account, you do it once.

• ChatGPT: Settings → Connectors → enable developer mode at the bottom of the page → add https://mcp.tecrube.com/mcp as a custom MCP server. Web interface and paid plans only.
• Claude Code: run claude mcp add --transport http tecrube https://mcp.tecrube.com/mcp in the terminal, then authenticate with /mcp.
• Cursor, VS Code, Windsurf: add { "mcpServers": { "tecrube": { "url": "https://mcp.tecrube.com/mcp" } } } to the mcp.json file and reload the window.

Credits and plans

The free trial includes 75 credits that never expire, with no card required. Each action spends credits by weight: reports and audits cost little, live changes such as building a campaign cost slightly more. Connecting an account and checking your balance cost nothing.

Pro ($49/month) is built for a single ad account; Agency ($99/month) for every client account under a manager account. Whatever the plan, preview, approval and the audit log work the same way.