Connect Google Ads to Claude Code with one command

One command, not a settings screen

The whole setup is one line in the terminal: claude mcp add --transport http tecrube https://mcp.tecrube.com/mcp. The default scope registers the server for the project you are in; -s user makes it available in every project on the machine; -s project writes a shared .mcp.json file that teammates pick up with git pull.

No package to install, no local process to keep running, nothing to maintain. The only thing that enters .mcp.json is a public address; committing it leaks no secret.

Your ad account and your repository in the same context

Only a coding agent can do this. Claude Code can read the conversion events your analytics module actually fires and compare them with the conversion actions defined in Google Ads; match the final URLs of live ads against the routes in your app and flag the ones that would 404; audit tracking templates against the UTM standard in your code.

A browser assistant cannot see the repo, and a reporting connector cannot see the code. In the terminal the output is not a screenshot but a file or CSV you can commit.

Recurring account work becomes a cron line

Headless mode, claude -p, turns weekly ad operations into a scheduled job: dump last week's spend into a dated markdown file, diff it against the previous run, put the summary in a pull request description.

One detail to know first: in headless mode Claude Code does not approve MCP tools on its own. With the --allowedTools flag you name the Tecrube tools that run may use. If you allow only the reporting tools, the job runs unattended and no scheduled run can ever touch spend.

Guardrails sized for an agent that already has shell access

Claude Code can already edit files and run commands; handing it unlimited spending authority on top would be a bad idea. So every tool with write access first returns only a preview: which account, which entity, current value, proposed value. The change reaches the platform only on the second, approved call.

A single change cannot raise a budget by more than 50%, and every applied action is written to an audit log. Because the gate sits on the Tecrube server rather than in the client, it behaves identically in the terminal, the browser and the editor.

Manager-account sweeps, on the Agency plan

The manager (MCC) structure is supported directly through login-customer-id; on the Agency plan one request can sweep every client account and return a single ranked answer: accounts missing conversion tracking, campaigns with runaway budgets, campaigns with no active ads.

The free trial and the Pro plan are deliberately locked to one ad account; cross-account sweeps are an Agency feature, while single-account audits work on every plan.

Set it up in 60 seconds

Four steps; the browser opens once in step two, the rest stays in the terminal.

• 1. Add the server: claude mcp add --transport http tecrube https://mcp.tecrube.com/mcp. Add -s user for all projects or -s project to share it with the team.
• 2. Authenticate: start Claude Code, type /mcp, select the tecrube server and choose Authenticate. A browser opens; sign in with Google and pick the ad account. Working over SSH on a server without a browser? Open the printed authorisation URL on your own machine.
• 3. Verify: run claude mcp list and confirm the server shows as connected, then ask the session to list your ad accounts. Meta, Microsoft, TikTok and LinkedIn sit on the same connector; each opens with its own one-time authorisation.
• 4. Run a real job: audit the last 30 days and have the findings written to a file in the repo. Reads return instantly; when the agent proposes a change, the preview is printed and waits for your approval.

Ask in plain English

• “List my Google Ads accounts, then write the last 30 days of campaign performance with spend, conversions and CPA columns to reports/google-ads.md.”
• “Compare the conversion actions in Google Ads with the events this repo's code actually fires; tell me which ones never fire.”
• “Compare the final URLs of all live search ads with the routes in this app; flag the ones that would 404.”
• “Pull the last 14 days of search terms, prepare a phrase-match negative list and show the preview before applying.”
• “Write a cron line that runs claude -p every Monday, allowlists only Tecrube reporting tools and dumps last week's spend into a dated markdown file.”