Platform
Four products, one sign-in
Google Ads, Analytics, Search Console and Tag Manager on one connector, under your own Google sign-in.
- Live
- Your own Google sign-in
- One connector
What is under it
Four products, counted
Each product is its own consent and page; its tools are listed from day one and work once you grant it.
- Google AdsLive
- Read, audit and change Google Ads from your AI client. It cannot delete, and nothing changes until you allow it.54 tools, usable once Google Ads is connected
- Google AnalyticsLive
- Run GA4 reports and create conversion events, custom dimensions and metrics from your AI client.23 tools, usable once Google Analytics is connected
- Search ConsoleLive
- Read search performance, inspect a URL, request indexing and submit a sitemap.6 tools, usable once Search Console is connected
- Tag ManagerLive
- Audit a container and stage the fix in Tag Manager. You publish the version yourself, then verify.18 tools, usable once Tag Manager is connected
- All four at once
- One connector, one sign-in, and every product's tools listed from day one; each one runs once you grant its product. Each grant is separate, and each one can be withdrawn on its own.103 tools on the full tier, whichever products are connected, as of v2.16.0
How it fits
One connector in the middle
Your assistant talks to one connector, the connector talks to each product, and your own Google sign-in is what allows it.
Google Ads
Google Analytics
Search Console
Tag Manager
Claude
ChatGPT
Microsoft Copilot
Claude Code
Codex
Gemini CLI- Any MCP client
Next on the roadmap
- next
Meta - next
Microsoft - nextAmazon
- nextTikTok
- next
X - next
LinkedIn - nextFlipkart Ads
For developers: Google Ads MCP server
Illustrative session
Access
What you actually grant
Stated in the words you would use, because you are being asked to make a decision here.
- What you are granting
- One Google sign-in, and then a separate consent per product. Granting Google Ads does not grant Analytics, Search Console or Tag Manager.
- What it can never widen
- It runs as you. If you cannot open an account or a property in Google's own interface, the connector cannot reach it either, and no setting on our side changes that.
- Where the grant lives
- In your own Google account, on its permissions page, where you can withdraw it at any moment without asking us first.
Start with Google Ads and add the others when you want them. Each product is its own consent, granted and withdrawn in your own Google account.
Google is still reviewing these permissions, so the consent screen may warn you that the app is not verified. You are granting access to your own account either way, and you can withdraw it from your Google account at any time.
Questions
Three short answers
The three things people ask before they connect this one, answered without hedging.
No. Google Ads on its own is a working connector; the other three add what they add. Each is a separate consent in your own Google account, and withdrawing one leaves the rest exactly as they were.
One sign-in, then a consent per product. The connector uses that grant for whichever products you turned on, and it can never reach an account your own Google login could not already open.
In your AI client. It asks our server, our server checks the connector, the tier and the account, then calls Google with your credential and hands the answer back. Nothing is copied into a dashboard of ours along the way.