Claude reads Google Ads through Google's read-only MCP server and site traffic through the Google Analytics MCP server, then drafts a short weekly check that you verify before anyone changes a budget.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For comparing ad and site-analytics extracts.
Analysis choices do not replace Google access; align attribution and dates. Choose one for analysis of a reviewed data extract; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Inspectable calculations come before narrative convenience. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Record export date, filters and units; save calculations with the result. The source ledger still needs reconciliation.
Reviewed 2026-10-21. This page applies a shared comparison for “analysis of a reviewed data extract” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Drafts a summary of no more than 150 words that flags week-over-week changes
AI platformConfirmed
04
You
Check the figures in each product's own dashboard and decide on any change
Human stepConfirmed
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
You verify the numbers and make any budget change yourself.
Watch out for
Ads and Analytics count conversions differently (attribution, time zones, reporting lag), so the two won't match exactly. The Analytics server is experimental. Neither server changes campaigns, so any budget change stays a manual step.
Starter prompt
Using the Google Ads MCP server, get last week's and the prior week's cost, clicks and conversions by campaign. Using the Google Analytics MCP server, run a report for the same dates with sessions and key events by session source. Write a summary of no more than 150 words, flag changes over 20%, and list anything that doesn't line up between the two. I'll check the numbers and decide on any changes.
Written for this workflow. Paste it into your AI platform and adjust it to your situation.
Google Ads: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Google Analytics: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Google Ads: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Google Analytics: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Google Ads: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Google Analytics: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Google Ads: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Google Analytics: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Gemini
To verify
Google Ads: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Google Analytics: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Google Ads: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Google Analytics: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked (2026-10-18)
Google Ads MCP server. Google’s developer guide describes an open-source server that reads account data with GAQL queries. Its tools cover search, resource metadata and the customers you can access. It reads only, so it can’t pause campaigns or change bids. It runs locally or over Streamable HTTP and needs Google Ads API credentials.
Google Analytics MCP server. Google’s repository runs a local server on the Analytics Admin and Data APIs. Its tools include account summaries, standard reports, funnel reports and a list of linked Google Ads accounts. Google calls it experimental.
Set it up
Set up API access for Google Ads and Google Analytics with an account that can only read the properties you need.
Add both servers to Claude, then run the prompt above once a week.
Check the totals in Google Ads and Google Analytics themselves. Expect differences from attribution models, time zones and reporting lag. Don’t add conversions from the two tools together.
Decide on any change in Google Ads yourself, and note why.
This is a proposed sequence based on documented tools, not a tested account integration.
Related agent skills
Google publishes two skills that fit this check. Google Ads Account Diagnostics gives an agent GAQL routines for conversion drops and lost impression share over the same read-only server. Google Analytics Data API Basics covers scripted GA4 reports. IonBin reviewed both from source only and didn’t run them.