About drift-mcp
drift-mcp is an MCP server published by Use-Tusk in the Other category.
The repository has 5 stars and 2 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/Use-Tusk/drift-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (6)
aggregate_spansCalculate latency percentiles, error rates, counts
Parameters not published.
get_schemaGet structure/schema of captured traffic
Parameters not published.
get_spans_by_idsFetch specific spans with full payloads
Parameters not published.
get_traceView distributed traces as hierarchical trees
Parameters not published.
list_distinct_valuesDiscover available endpoints and field values
Parameters not published.
query_spansSearch API traffic with flexible filters
Parameters not published.
Ask AI
Ask AI about drift-mcp
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
Tusk Drift MCP
An MCP server for querying API traffic data captured by Tusk Drift. This enables AI assistants to search, analyze, and debug your application's API traffic, including HTTP requests, database queries, and distributed traces.
New to Tusk Drift? Check out our docs and sign up for an account.
Setup
Option 1: Remote MCP Server (Recommended)
Connect directly to the hosted Tusk Drift MCP server. This is the easiest setup and doesn't require running anything locally.
For Cursor:
Add to your Cursor MCP settings (~/.cursor/mcp.json or workspace .cursor/mcp.json):
{
"mcpServers": {
"tusk-drift": {
"url": "https://api.usetusk.ai/api/drift-mcp",
"headers": {
"x-api-key": "YOUR_TUSK_API_KEY"
}
}
}
}
For Claude Code:
Option A — CLI command:
claude mcp add --transport http tusk-drift https://api.usetusk.ai/api/drift-mcp \
--header "x-api-key: YOUR_TUSK_API_KEY"
Option B — Add to .mcp.json in your project root:
{
"mcpServers": {
"tusk-drift": {
"type": "http",
"url": "https://api.usetusk.ai/api/drift-mcp",
"headers": {
"x-api-key": "YOUR_TUSK_API_KEY"
}
}
}
}
For Claude Desktop:
{
"mcpServers": {
"tusk-drift": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.usetusk.ai/api/drift-mcp"],
"env": {
"MCP_HEADERS": "{\"x-api-key\": \"YOUR_TUSK_API_KEY\"}"
}
}
}
}
Option 2: Local Installation (via NPX)
Run the MCP server locally. This is useful if you need offline access or custom configuration.
For Claude Desktop / Cursor:
Add to your claude_desktop_config.json or Cursor MCP settings:
{
"mcpServers": {
"tusk-drift": {
"command": "npx",
"args": ["-y", "@use-tusk/drift-mcp"],
"env": {
"TUSK_API_KEY": "YOUR_TUSK_API_KEY"
}
}
}
}
Configuration (env vars for local installation)
| Variable | Required | Description |
|---|---|---|
TUSK_API_KEY |
Yes | Your API token |
TUSK_DRIFT_API_URL |
No | Backend base URL (defaults to https://api.usetusk.ai). Use origins like https://api.usetusk.ai or http://localhost:8000, not /api/drift-mcp. |
TUSK_DRIFT_SERVICE_ID |
No | Service ID (auto-discovered from .tusk/config.yaml if not set) |
TUSK_WORKSPACE_ROOTS |
No | Comma-separated workspace roots to search for .tusk/config.yaml files when auto-discovering services |
Available Tools
| Tool | Description |
|---|---|
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 |
Support
Need help? Open an issue or contact us at support@usetusk.ai.
License
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.