The TrueClicks MCP lets you query your TrueClicks data and your linked Google, Microsoft, and Meta Ads accounts from your AI or automation tool. It has Google Ads, Microsoft Ads, and Meta Ads MCPs built in, so one connection covers all of them plus your TrueClicks data. For what it is and what data it reaches, see Using the TrueClicks MCP.
The MCP URL is:
https://data.trueclicks.com/mcp/
Everything is read-only: reporting and analysis only, no changes to your accounts or ad platforms.
n8n runs unattended, so it authenticates with a data connector key rather than a login. You create a key in TrueClicks and give n8n the token as a bearer token.
Before you start
In TrueClicks, go to Admin > Export TrueClicks data and create a data connector key. Each key has a name and a token.
Scope the key when you create it: all your linked accounts, or a subset by client label.
Copy the token.
Treat the token like a password. Anyone who has it reaches every account the key is scoped to. Keep it in a Make.com connection, not typed into each module.
Steps
Add the MCP module in your scenario (or an HTTP/MCP client module that lets you set headers).
Set the server URL to
https://data.trueclicks.com/mcp/.Add an Authorization header with your token as a bearer value:
Authorization: Bearer YOUR_TOKEN.Map the TrueClicks tools into your scenario.
Good to know
If a key leaks, delete it under Admin > Export TrueClicks data and create a new one. The old one stops working.