Answers from live data, not exports
Ask in plain words and Claude queries the accounts directly. No CSV exports, no copying numbers into a chat.
Your marketing data, inside Claude
A remote MCP connector that gives Claude your GA4, Google Ads, Search Console, Tag Manager, BigQuery and Yandex accounts. Deployed on your server, under your accounts, behind one login.
97 toolsWrites only after you confirmWeb, desktop and mobile
ClaudeMarketing connector
Which campaigns spent last week without a single conversion?
Google Ads: run query
Illustrative interface with sample data. No live account is connected.
Eight platforms, 97 tools
Reads work out of the box. Changes to Google Ads and Yandex Direct exist too, behind a confirm step you control.
47
GA4
Reports, funnels, events, audits and read-only admin.
17
Google Ads
Queries and audits, plus campaign changes behind a confirm step.
7
Search Console
Search analytics, URL inspection and sitemaps.
5
Tag Manager
Containers, workspaces and entity search.
4
BigQuery
Datasets, tables, schemas and queries.
3
Data Manager
Identifier preparation, event validation and request status.
4
Yandex Metrica
Counters, goals and reports.
10
Yandex Direct
Campaigns, ads, keywords and reports, with edits behind a confirm step.
What changes for your team
Changes wait for your confirm
Every write first returns the planned change and runs only when you confirm it. Google Ads changes are validated by Google before they apply.
One login on every device
The login lives in your Claude account. Switch from laptop to phone and the same accounts are there, with nothing to authorise again.
Credentials stay on your server
Tokens are created once during setup and stay on your server, in a service locked down to a single folder. Laptops never hold them.
Illustrative interface with sample data. No live account is connected.
Deployed for your team
- 1A 30-minute call and an access list
- 2Deployment on your server or cloud
- 3Claude connected and a walkthrough
Your connector, your accounts
- Runs on your own server or cloud account
- Uses your Google and Yandex credentials, never mine
- Writes stay off until you decide to switch them on
- Updates when Google or Yandex change their APIs
Fixed priceQuoted after a 30-minute call, once we know the accounts and where it should run.Book a setup call
Want someone to read the data with you? The fractional retainer adds analysis on top of the connector.
Questions people usually ask
Where do the credentials live?
On your server, in a folder only the connector's service account can write to. Tokens are created once during setup, and laptops never hold them.
Can Claude change campaigns on its own?
No. Writes are off unless you switch them on for your deployment. Even then, every write first returns the planned change and runs only when you confirm it, and Google Ads changes are validated by Google before they apply.
Which Claude apps work with it?
Claude on the web, desktop and mobile, as a custom connector on a Claude plan that supports them. The login is stored in your Claude account, so there is nothing to set up per device.
Do you keep access to our data?
The connector runs under your accounts on your server. I need access during setup; after that, you decide whether I keep it.
Who can log in?
Each deployment has one user, protected by OAuth 2.1 with PKCE. Ask for separate deployments when analysts need separate access.
What happens when Google or Yandex change their APIs?
Updates are part of support. New tool sets plug in without touching the ones that already work.
Put your marketing data in Claude
A 30-minute call to check your accounts and decide where the connector should run.