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.
If your tool isn't covered by its own page, this guide walks through the connection methods so you can pick the right one. The MCP works over streamable HTTP.
Which method to use
The TrueClicks MCP supports four ways to authenticate. Use the first one your tool supports, in this order:
OAuth for AI chat assistants.
Bearer token for automation tools.
Basic auth if the tool can't do bearer.
Token in the URL only as a last resort.
Pick one and use it. You don't combine them.
OAuth (recommended for AI chat assistants)
If your tool is an AI assistant that supports MCP with OAuth (most do), use this. You don't handle any secrets, and you connect as yourself, so the assistant reaches exactly the accounts your TrueClicks access allows.
Add a custom connector or MCP server in your tool.
Enter the URL
https://data.trueclicks.com/mcp/.Choose OAuth. The tool sends you to TrueClicks to log in and approve access.
Bearer token (recommended for automation tools)
For unattended tools (workflows, scripts, schedulers) that can't log in, use a bearer token. First create a data connector key in TrueClicks under Admin > Export TrueClicks data. Each key has a name and a token, and you scope it to all accounts or a subset by client label.
Point your tool at the URL
https://data.trueclicks.com/mcp/.Add an Authorization header with your token as the bearer value:
Authorization: Bearer YOUR_TOKEN. The key name isn't needed.
Treat the token like a password. Anyone who has it reaches every account the key is scoped to, so keep it in the tool's secret store and don't share it.
Basic auth (if bearer isn't available)
Some tools only offer basic auth (a username and password field). Use your data connector key here: the key name is the username, the token is the password. Point the tool at https://data.trueclicks.com/mcp/ and enter those two values.
Token in the URL (last resort)
A few tools accept nothing but a URL, with no header or auth fields. For those, put the token in the URL itself:
https://data.trueclicks.com/mcp/YOUR_TOKEN
Use this only when there's no other option. The token sits in the URL, so it's easier to leak (in logs, browser history, or a shared link) than a bearer token kept in a secret store. If your tool supports OAuth, bearer, or basic auth, use one of those instead.