Trackdesk MCP Server

1. Connect with OAuth (recommended)

Point your AI app at https://mcp.trackdesk.com/api/mcp and let it authorize. Apps that support OAuth discover everything they need automatically, so there is nothing to copy and paste:

{
  "mcpServers": {
    "trackdesk": {
      "url": "https://mcp.trackdesk.com/api/mcp"
    }
  }
}

On the first request the server replies with a 401 and a WWW-Authenticate challenge pointing at its protected resource metadata, which in turn names the authorization server. Your app then runs the standard authorization-code flow with PKCE.

Apps that cannot register themselves can be set up by hand under Settings → Integrations → OAuth2: create Public OAuth2 credentials with the redirect URI your app uses and give it the resulting client_id.

2. Or use an API key

For apps without OAuth support, generate a key under Settings → Integrations → Personal tokens and send it as a header:

{
  "mcpServers": {
    "trackdesk": {
      "url": "https://mcp.trackdesk.com/api/mcp",
      "headers": {
        "X-Api-Key": "YOUR_API_KEY"
      }
    }
  }
}

3. Start using it

Your AI assistant can now search and work with the Trackdesk API. Reading and each kind of change go through a tool of their own, so your app can let reads through and ask you before anything changes:

• search — find API endpoints and their request schemas
• read_data — read data
• create_data — create records and record tracking events
• update_data — change existing records
• delete_data — delete records

Your app gets only the tools your account can use.