Home/Paid ads/Google Ads MCP for Coding Agents, Spend on Approval

Waste less ad spend on untracked clicks

Tin's Google Ads MCP connection puts the ad account beside your site's repository, so the coding agent can check pages and tracking before launch. Budget and bidding changes wait for approval. Our paid ad consultants can take on the campaigns and the pages behind them.

Book a call

Check the site beside the ad account
System view
Tin's System view: scheduled and available workflows for a project

What is a Google Ads MCP server?

A Google Ads MCP server makes an ad account's reports and settings available as tools an AI agent can call. MCP connects the agent to those outside tools while it works in Claude Code, Codex or Cursor. The agent can then answer a campaign question from the ads, search terms and spending it reads. Each server defines which account changes it allows and which other systems the agent can reach.

An exported report suits a question about a particular campaign. A server exposing account tools supports campaign questions in plain language. Tin places the account beside keyword data and the site's repository, with jobs that assess, plan, launch and monitor Google Search campaigns. Compare who approves budget changes and whether the landing page and conversion tag can be fixed where the agent works on the ads.

Ads run apart from your site lose paid clicks

An agent changes the campaign while the landing page and its conversion tracking remain outside the account it can see.

  • Clicks go unmeasured. Without a recording conversion action, visits cannot show which ads led to the intended action.
  • Waste keeps spending. Irrelevant search terms continue to take budget until someone excludes them.
  • Broad matches miss buyers. Wide keywords can buy searches for needs the product does not serve.

Access to the repository lets the agent inspect the landing page and conversion event before launch.

Tin reads the account and the site together

Before it drafts a campaign, Tin checks whether the account can launch and the site can record the response.

Check the account before planning

Tin checks the manager link, billing, landing page and a conversion action that records data. The plan follows those checks. If the account has no recording conversion event, the agent can inspect the site code and propose tracking work before the campaign starts.

Inspect the account and landing page
Project files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Fix tracking in the repository

If conversions are not being recorded, Tin pauses the launch and offers a tracking setup. With GitHub connected, that includes a pull request to add the site tag. The proposed code change gives the engineer a specific fix to inspect before running the launch again.

Inspect the exact campaign plan

The plan includes ad groups, exact and phrase keywords, headlines, descriptions, sitelinks, negatives, budget and a click ceiling. It is saved under ads/google in project Files. Once approved, Tin creates that campaign in a validated request to the company's own Google Ads account.

Read the campaign before creation
Project files
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Remove waste from search terms

The monitor reads performance and search terms, adding negative keywords up to the limit set for each run. It can pause disapproved ads and wasteful keywords. Because the agent can read the product code, it has context for judging an unfamiliar search term against what the company sells.

Review the searches taking budget
Week view
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

Decide budget and bidding changes

A suggested budget or bidding change arrives as a proposal. Tin waits for approval before applying it, while the current settings remain in place. Discard the proposal and those settings stay as they were. Open the report under ads/google to read what the monitor found and which changes it proposed.

Workflows cover ads from fit check to upkeep

Assess Google Search

Get a verdict, scorecard and campaign shape based on the business and site. See the assessment

Launch the approved campaign

Create the exact Google Search plan in the company's own ad account. See campaign launch

Check campaign performance

Read search terms and prepare budget proposals while handling the permitted cleanup. See campaign check-ups

Research keyword demand

Build a buyer-search inventory with evidence for the campaign's keyword choices. See keyword research

Audit destination pages

Check technical SEO and AI visibility on the site receiving paid visits. See the site audit

Summarise the week's activity

Read completed runs and open items before choosing the next campaign task. See project summaries

  • Google Ads
  • Claude Code
  • Codex
  • Cursor
  • GitHub
  • Google Search Console
  • PostHog

Check ads fit, then choose who runs them

The assessment can start with a public site and a measurable action. An ad account is needed when the work reaches launch.

Assess whether search ads fit
System view
Tin's System view: scheduled and available workflows for a project

Assess before connecting Ads

Add Tin to Codex, then ask whether Google Search fits the business; the assessment gives advice without changing an account.

codex mcp add tin --url https://app.tin.computer/mcp

Connect for campaign creation

Enter the customer ID and accept Tin's manager invitation in Google Ads to launch the approved plan.

Hand campaigns to consultants

We run Google, Bing and LinkedIn ads, build the landing pages and tune budgets each week.

Every ads workflow is code you can read

Read the code

The paid ads assessment and campaign launch steps are text in the repo.

Run it on your machine

Connect your own Google Ads account and run the checks on your schedule.

Change a workflow

Change a campaign rule in the file and return it as a pull request.

Open source, Apache 2.0

Talk to Tin

We can discuss the campaign, landing page and tracking work our paid ad consultants would run, including Google, Bing, LinkedIn and remarketing. They plan the searches and tune the budget each week.

Book a call

FAQ

How does Tin get access to our Google Ads account?

You enter the customer ID and accept an invitation from Tin's manager account inside Google Ads. The campaign is then created in your company's account after the exact plan is approved. The connection lets the launch check billing and tracking before creating that campaign.

What happens if we have no conversion tracking?

Missing conversion tracking blocks the launch. Tin offers a tracking setup for approval first, including a site-tag pull request when GitHub is connected. Once the conversion action records data, the launch can run again against the account and the page with tracking in place.

Does it cover Bing or LinkedIn ads?

The assessment and campaign-launch jobs cover Google Search. Our paid ad consultants also run Bing and LinkedIn ads as part of the service. We can discuss those channels with the landing pages and tracking they need, then decide which campaign work to take on.

How often does the check-up run?

Choose an on-demand, daily or weekly check once the campaign launched through Tin is live. Each run reads performance and search terms and leaves a report under ads/google. The schedule controls when the check runs; a proposed budget or bidding change still needs approval.

Plan your first Google Search test with us

Talk with the founders and engineers who run the experiments, with paid ad consultants on the team. We can discuss whether your site supports a useful Google Search test and which searches would give it a starting point.

Book a call