Connect your favorite AI assistant directly to your Trackdesk account using the Model Context Protocol (MCP). Once connected, the assistant can both read your data and make changes to it. It can search your affiliates and pull conversion reports, but also approve conversions, update offers, or set up payouts, all from a conversation.
The Trackdesk MCP server is hosted for you. There is nothing to install or run locally. You add one URL to your MCP client, sign in to Trackdesk, and approve the access.
Using Claude or ChatGPT? Follow Connect Trackdesk to Claude or Connect Trackdesk to ChatGPT instead.
What you can do with it
The MCP server exposes the Trackdesk public API to any AI assistant that supports MCP, including Claude, ChatGPT, Cursor, Windsurf, and others. Your assistant is not limited to reading data. It can also create, update, and delete records in your program, the same way an API integration would.
Read and analyze
Asking questions about your program data in natural language ("How many approved conversions did we have last week?")
Generating reports or summaries of affiliate performance
Prototyping API integrations before writing any code
Make changes
Approving, rejecting, or updating conversions ("Approve all pending conversions from affiliate X that are older than 30 days.")
Registering affiliates and changing their status or tier
Creating and editing offers, including pricing, landing pages, and creatives
Creating coupons and giving affiliates access to offers
Adding affiliate bonuses and creating settlements for payouts
Setting up webhooks and tags
Your assistant acts as the Trackdesk account you sign in with and has exactly its permissions. Affiliates and advertisers can connect too, and their assistant sees only their own data. See Connect to Trackdesk: API, MCP and AI Assistants.
Before you start
You will need:
A Trackdesk account. Admins and team members can connect right away. Affiliates and advertisers can connect when the program allows it.
An MCP-compatible AI client
Your Tenant ID, the subdomain you log in with
Connect your client
The MCP server is available at the /mcp path on your Trackdesk subdomain. For clients that store MCP servers in a configuration file, add this entry:
{
"mcpServers": {
"trackdesk": {
"url": "https://TENANT_ID.trackdesk.com/mcp"
}
}
}Replace TENANT_ID with your Tenant ID.
In Claude Code, run:
claude mcp add --transport http trackdesk https://TENANT_ID.trackdesk.com/mcp
On the first request, your client opens the Trackdesk sign-in page. Sign in, check the application name, and click Allow access. Clients that support OAuth find everything else automatically, so there is nothing to copy and paste.
If your client can't register itself, create Public credentials in Settings → Integrations → OAuth2 with the redirect URI your client uses, and give it the resulting client ID. See OAuth2 Credentials.
Connect with an API key instead
For clients without OAuth support, generate a personal token and send it in the X-Api-Key header:
{
"mcpServers": {
"trackdesk": {
"url": "https://TENANT_ID.trackdesk.com/mcp",
"headers": {
"X-Api-Key": "API_KEY"
}
}
}
}Replace these values:
TENANT_ID: your Tenant IDAPI_KEY: your personal token
Restart your MCP client after saving the configuration.
How your assistant uses it
Once connected, your AI assistant gains two tools that together cover the Trackdesk API:
search: Discovers available API endpoints by keyword. The assistant uses this to find the right endpoint for your request, for example looking up how to list affiliates or create a conversion.
execute: Calls any API endpoint, whether it reads data or makes a change, on your behalf.
You do not need to know any of the endpoint names or parameters yourself. Ask the assistant what you want in plain language, and it will pick the correct calls.
Verify the connection
To confirm everything is working, open a new conversation in your MCP client and ask something that requires data from your program, for example:
"List the last five affiliates that joined my Trackdesk program."
"Show me approved conversions from the past seven days."
"Set up creating conversions based on stored Trackdesk CID."
The assistant announces that it is calling the Trackdesk tools and returns the results in the conversation. If you see an authentication error, reconnect and approve the access again, or, with an API key, check that the X-Api-Key value matches a token that has not been revoked.
Review changes before they run
⚠️ Important: Changes made through the assistant take effect immediately in your live program, exactly as if you made them in the dashboard or through the API.
To stay in control:
Keep your client's tool approval prompts on, so you confirm each action before it runs
For bulk changes, ask the assistant to list the affected records first, then confirm
Connect with an account whose permissions match what the assistant should be allowed to do
Security and permissions
To disconnect an assistant, navigate to Settings → Integrations → OAuth2, open the Admin tab, find the assistant's credentials (owner Registered by the application itself) and click Delete on the row. Affiliates and advertisers delete the assistant's credentials under Tools → Integrations → OAuth2. Its access stops immediately.
If you use an API key, treat it like a password: keep it out of shared or version-controlled files, and revoke it from the Personal tokens screen if it is exposed.
All requests from the MCP server to the Trackdesk API are made over HTTPS, and your credentials are forwarded on every call. They are never stored by the server.
Related
AI Assistant: the assistant built into your dashboard, no connection needed.