Reference
Configuration
Every SDK option, the data captured on each call, and the metrics TrackMCP computes from it.
SDK options
OptionTypeDefault
apiKeystringrequired
Your workspace ingest key.
servicestring"mcp-server"
Name shown for this server.
environmentstring"production"
Splits data by environment.
sampleRatenumber1.0
Fraction of calls captured (0-1).
redactstring[][]
Argument/result paths to strip locally.
endpointstringtrackmcp.com/api/v1/ingest
Override for self-hosted ingest.
disabledbooleanfalse
Turn capture off without removing the wrapper.
What gets captured
On every tool call, the wrapper records the following. Arguments and results pass through your redact rules first, in your process.
- Tool name and the arguments (after redaction)
- Result payload and whether it carried isError: true
- Client type (Claude, Cursor, ChatGPT, custom)
- Duration in milliseconds and transport status
- Session id, so calls can be inspected in order
- Timestamp and environment
Metrics TrackMCP computes
- Active clients, new and returning connections
- Completed workflows and completion rate
- Tool call volume, adoption, and week-over-week change
- p50 / p95 latency and error rate per tool
- Silent failures (errors inside a 200 OK)
- Most common workflows and where sessions stop
Environment variables
Python reads TRACKMCP_KEY automatically when an API key is not passed. TypeScript requires apiKey in the options. For a self-hosted deployment, pass the ingest URL explicitly as endpoint;TRACKMCP_ENDPOINT is not read automatically.