The TrueClicks MCP lets you query your TrueClicks data and your linked Google, Microsoft, and Meta Ads accounts straight from an AI platform like Claude or ChatGPT, or any other tool that supports MCP connectors. You ask in plain language, it pulls the data and answers. No coding, no exporting, no jumping between screens.
This page covers what it is and how to set it up. For ideas on what to do with it, see the use cases page. This page is for PPC specialists.
Built-in platform MCPs
The point worth knowing up front: the TrueClicks MCP has Google Ads, Microsoft Ads, and Meta Ads MCPs built in. Your TrueClicks data and all three platforms come through one connection, so you don't set up or maintain a separate MCP per platform.
What you need
An AI platform that supports MCP connectors. Claude (claude.ai or the desktop app) and ChatGPT both do, and so do a growing number of others.
A data connector token from TrueClicks. Authentication works by putting this token in the MCP URL:
https://data.trueclicks.com/mcp/{YOUR_DATA_CONNECTOR_TOKEN}The token is part of the URL, so treat the whole thing as a password. Create and manage data connectors in TrueClicks under Admin > Export TrueClicks data.
Connecting
Same idea in every tool: add a new MCP connector, name it, paste your URL. No separate password, the token is in the URL.
The exact wording differs between platforms, but the steps are the same:
Claude (web or desktop): open your connector settings, add a custom connector, paste the URL, and connect.
ChatGPT: add it as a custom connector / MCP server and paste the URL.
Other platforms: look for "MCP servers," "custom connectors," or "integrations," then add the URL.
Once connected, you can start asking.
Scoping what a connector can reach
A data connector token controls which accounts come through it. You can create a connector that reaches all your linked accounts, or scope it to a specific subset of client accounts using a client label. That lets you, for example, give one connector access to a single client's accounts and keep it separate from the rest. The AI platform only ever sees the accounts the connector is scoped to.
What data you can reach
From TrueClicks
Monitoring errors: the errors and issues TrueClicks monitoring has flagged across your accounts, such as broken URLs and tracking problems.
Audits: your latest audit results and insights, scored at account level, per rule, and per campaign, plus the full detail behind each finding and historical runs so you can see how things have moved.
Budget pacing: your current pacers and whether accounts are tracking ahead or behind, across all periods.
Tasks: open and completed tasks across your accounts.
Accounts and users: the accounts and labels you have access to, your users, and which account each user has selected as their "my account."
From your ad platforms
The MCP reads live performance and configuration data from the platforms linked to your TrueClicks accounts. It's read-only across all three.
Google Ads: any performance or entity data you'd normally report on, by campaign, ad group, keyword, and so on, over any date range.
Microsoft Ads: performance reports over a date range, plus account and campaign configuration.
Meta Ads: performance and insights data per account.
The MCP makes no changes, and is only for reporting and analysis.
Tips for good results
Name the account. If you have many, ask it to list accounts first, then point at the one you mean.
Be specific on date range and metrics. "Last 30 days, cost and conversions by campaign" beats "how are things doing."
Ask for a summary when you want the headline, the detailed table when you want raw rows to work with.
Security
Your URL contains the connector token. Don't share it, paste it in public chats, or commit it anywhere.
All tools are read-only. Nothing can be edited, paused, or changed through the MCP.
A connector only reaches the accounts it's scoped to. If you only need one client's accounts, scope the connector to that client label rather than all accounts.
If a token leaks, delete or regenerate the data connector in TrueClicks. The old URL stops working.