Drift

You run an MCP server that lets you query and analyze API traffic data captured by Tusk Drift. It enables you to search HTTP requests, database queries, and distributed traces, making it easier to debug, monitor, and reason about your application's API activity.

How to use

Connect your MCP client to either the hosted remote server or run a local instance and use the available commands to query traffic data. You can access the remote MCP endpoint for convenient, hosted access, or run the MCP server locally if you need offline access or custom configurations. Use the remote endpoint for day-to-day usage and switch to the local server when you require offline access or full customization.

HTTP remote config (recommended)

{
  "mcpServers": {
    "tusk-drift": {
      "url": "https://api.usetusk.ai/api/drift-mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TUSK_API_KEY"
      }
    }
  }
}

Local installation (using NPX)

Install and run the MCP server locally so you can access it offline or with custom settings.

npm install -g @use-tusk/drift-mcp

Claude Desktop / Cursor config for remote access

{
  "mcpServers": {
    "tusk-drift": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.usetusk.ai/api/drift-mcp"],
      "env": {
        "MCP_HEADERS": "{\"Authorization\": \"Bearer YOUR_TUSK_API_KEY\"}"
      }
    }
  }
}

Claude Desktop / Cursor config for local run

{
  "mcpServers": {
    "tusk-drift": {
      "command": "npx",
      "args": ["-y", "@use-tusk/drift-mcp"],
      "env": {
        "TUSK_API_KEY": "your-api-token"
      }
    }
  }
}

Configuration (env vars for local installation)

Set the environment variables shown below to configure your local MCP server. These are the keys you will pass to the running process.

Environment variables

TUSK_API_KEY: Your API token (required)
TUSK_DRIFT_API_URL: Tusk API URL (optional, defaults to https://api.usetusk.ai)
TUSK_DRIFT_SERVICE_ID: Service ID (optional, auto-discovered from .tusk/config.yaml if not set)

Available tools

The MCP server exposes a set of tools to query and analyze API traffic. You can use these tools to search spans, inspect schemas, aggregate metrics, and retrieve traces.

Support

Need help? Open an issue or contact us at support@usetusk.ai.

License

MIT

Notes

If you need additional configuration or have specific access requirements, you can combine the remote endpoint with local runs by using separate MCP client configurations for different environments.

Available tools

query_spans

Search API traffic with flexible filters

get_schema

Get structure/schema of captured traffic

list_distinct_values

Discover available endpoints and field values

aggregate_spans

Calculate latency percentiles, error rates, counts

get_trace

View distributed traces as hierarchical trees

get_spans_by_ids

Fetch specific spans with full payloads