This page shows how to connect the TrueClicks MCP to the most common platforms. For what the MCP is and what data it reaches, see Using the TrueClicks MCP.
Before you start
Create a data connector key in TrueClicks under Admin > Export TrueClicks data. Each key has a name and a token. How you use them depends on the platform:
Bearer token: use the base URL and pass the token as a bearer token. The name is ignored.
Basic auth: use the base URL with the key name as the username and the token as the password.
Token in the URL: append the token to the base URL. This is the fallback for platforms that only accept a URL.
The base URL is always the same:
https://data.trueclicks.com/mcp/
All three methods are read-only. Scope the key to all accounts or a subset by client label when you create it.
Claude (web and desktop)
Claude (web and desktop)
Claude connects with the token in the URL.
Open Claude and go to your connector settings (Settings > Connectors, or Customize > Connectors).
Click to add a custom connector.
Give it a name "TrueClicks MCP" and paste the full URL with your token:
https://data.trueclicks.com/mcp/YOUR_TOKEN
Add it, then connect. On Team and Enterprise plans an Owner adds the connector first, then each member connects individually.
Enable it in a conversation from the connectors menu, and start asking.
ChatGPT
ChatGPT
ChatGPT connects with the token in the URL. Custom MCP connectors require developer mode, available on paid plans (Plus, Pro, Business, Enterprise, Edu) on the web. On Business and Enterprise, an admin enables developer mode first.
Enable developer mode under Settings > Connectors (or Apps) > Advanced settings.
Create a new connector / app for a custom MCP server.
Give it a name and paste the full URL with your token:
https://data.trueclicks.com/mcp/YOUR_TOKEN
Save, then enable the connector in a conversation. You may be asked to approve each tool the first time it runs.
n8n
n8n
n8n uses the MCP Client Tool node with a bearer token, so the token is separate from the URL.
Add an MCP Client Tool node to your workflow (connected to an AI Agent node).
Set the endpoint URL to the base URL:
https://data.trueclicks.com/mcp/
Set the authentication to Bearer and create a credential with your token as the bearer value. The key name isn't needed for bearer auth.
Choose which tools to expose (all, or a selected subset), and run your workflow.
Zapier
Zapier
Zapier connects to external MCP servers with the MCP Client app (currently in beta), using a bearer token.
On the Apps page, add a connection and search for MCP Client.
In the connect dialog, enter the server URL:
https://data.trueclicks.com/mcp/
Select the transport your setup uses, set OAuth to No, and paste your token in the Bearer Token field.
Finish connecting. The TrueClicks tools are then available as actions in the Zap editor.
Gemini
Gemini
The consumer Gemini app does not support custom MCP connectors, so you can't add the TrueClicks MCP there. Custom MCP is available in Gemini Enterprise (added as a data connector / data store) and in the Gemini CLI. If you're on one of those, follow Google's setup for adding a custom MCP server and use the base URL with your token.
Any other MCP platform
Any other MCP platform
Most other platforms follow one of the same three patterns. Point the client at the base URL:
https://data.trueclicks.com/mcp/
Then authenticate with whichever method the platform offers:
If it has a bearer token field, use the base URL and pass the token as the bearer token.
If it uses basic auth, use the key name as the username and the token as the password.
If it only takes a URL, append your token to the base URL.
https://data.trueclicks.com/mcp/YOUR_TOKEN
If the platform lets you pick a transport, the TrueClicks MCP works over streamable HTTP.