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.
Google Ads, Microsoft Ads, and Meta Ads are built in, so one connection covers TrueClicks and all three platforms. You don’t need a separate MCP per platform.
This page covers what it is and what you can reach. You can find step-by-step instructions for setting it up on each platform in the platform guides. For ideas on what to do with it, see What to use the TrueClicks MCP for.
Two ways to connect
| Sign in with TrueClicks (OAuth 2.0) | Data connector key |
Use it for | You, working in Claude, ChatGPT, or similar | Automations with no person signing in (n8n, Make.com, scheduled workflows) |
Who it acts as | You | The key, not a person |
Accounts it reaches | The accounts your TrueClicks user can access | All linked accounts, or one client label |
What you manage | Nothing. You sign in once | A token you store and protect |
Both use the same connector URL:
https://data.trueclicks.com/mcp/
Sign in with your TrueClicks account (recommended)
Sign in with your TrueClicks account (recommended)
Use this whenever a person is using the MCP. It’s the most secure option.
Add the connector URL in your AI platform.
Sign in to TrueClicks when your AI platform asks.
Approve access.
The MCP now works as you. To disconnect, remove the connector in your AI platform.
Use a data connector key (for automations)
Use a data connector key (for automations)
Use a key only when no person can sign in, for example, an n8n or Make.com workflow that runs on a schedule.
Go to Admin > Export TrueClicks data and create a key.
Choose whether it reaches all linked accounts or only accounts with a specific client label.
Add the token to your tool. Depending on the tool, that’s in the connection URL, as a bearer token, or the key name and token as basic auth. Each tool’s setup guide says which.
Important: Anyone with the token can use it. Don’t share it, paste it in chats, or commit it to code. Scope it to the smallest set of accounts the automation needs. If a token leaks, delete or regenerate the key, and the old token stops working.
Scoping what a connector can reach
A data connector key controls which accounts come through it. You can create a key 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 key access to a single client's accounts and keep it separate from the rest. The AI platform only ever sees the accounts the key 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 is read-only across all three: it makes no changes, and is only for reporting and analysis.
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.
Approving tool use
Most tools ask before they run, which is the safe default. Everything here is read-only: it pulls data but never changes anything in your accounts or ad platforms. If you trust a tool and don't want prompts, set it to always allowed in your tool settings.
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
The token authenticates as you. 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.