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 only need to generate a personal access token and paste a short configuration snippet into your MCP client.
Using Claude on the web, desktop, or mobile? Follow Connect Trackdesk to Claude instead. Claude connects through a connector rather than a configuration file.
What you can do with it
The MCP server exposes the full Trackdesk public API to any AI assistant that supports MCP, including Claude, 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 has access to the same endpoints as the public Trackdesk API, scoped to the permissions of the personal access token you provide.
Before you start
You will need:
A Trackdesk account with access to the Personal access tokens section
An MCP-compatible AI client that reads a configuration file (for example, Cursor or Windsurf)
Your Trackdesk subdomain, the URL you use to log in, in the form
https://your-tenant.trackdesk.com
Generate a personal access token
The MCP server uses a personal access token to authenticate requests on your behalf. Every call your AI assistant makes is forwarded to the Trackdesk API with this token.
Log in to your Trackdesk program
Navigate to Settings
In the Integrations section, navigate to Personal access tokens
Generate a new token and copy it somewhere safe, you will not be able to view it again
For more details on how personal access tokens work, see Personal tokens and API access.
Configure a config-file client
These steps apply to clients that store MCP servers in a configuration file. If you use Claude, see Connect Trackdesk to Claude instead.
The MCP server is available at the /mcp path on your Trackdesk subdomain:
https://your-tenant.trackdesk.com/mcp
Add the following entry to your MCP client configuration, replacing your-tenant with your Trackdesk subdomain and YOUR_API_KEY with the personal access token you just generated:
{
"mcpServers": {
"trackdesk": {
"url": "https://your-tenant.trackdesk.com/mcp",
"headers": {
"X-Api-Key": "YOUR_API_KEY"
}
}
}
}The exact location of this configuration depends on your client:
Cursor: edit the MCP servers section in Settings, under MCP
Windsurf: edit the MCP servers section in Windsurf settings
Restart your MCP client after saving the configuration. The Trackdesk server will appear in the list of connected tools.
How your assistant uses it
Once connected, your AI assistant gains two tools that together cover the entire Trackdesk API:
search: discover 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: call any API endpoint, whether it reads data or makes a change. The assistant uses this to actually run the action, with your personal access token attached automatically.
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 will announce that it is calling the Trackdesk tools and return the results in the conversation. If you see an authentication error, double-check that the X-Api-Key value matches the token you generated and that the token has not been revoked.
Review changes before they run
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
Generate the token from a user whose permissions match what the assistant should be allowed to do
Security and permissions
Treat your personal access token like a password. Anyone who has it can access the Trackdesk API on your behalf, with the same permissions as your user account.
Store the token only in your MCP client configuration, and keep that file out of shared or version-controlled locations
Do not share it in screenshots, chat messages, or public repositories
If a token is exposed, revoke it immediately from the Personal access tokens screen and generate a new one
All requests from the MCP server to the Trackdesk API are made over HTTPS, and your token is forwarded on every call. It is never stored by the server.