Reference

REST API

Query the analytics currently exposed by your workspace. Requests use the same TrackMCP domain as the dashboard.

Authentication

Send your API key as a bearer token. Keys are scoped to a workspace and can be read-only.

curl "https://trackmcp.com/api/v1/analytics?days=7" \
  -H "Authorization: Bearer $TRACKMCP_KEY"

Send telemetry

SDKs send canonical batches to the ingest endpoint automatically. You normally do not call it directly, but the wire format is useful when integrating another runtime.

curl https://trackmcp.com/api/v1/ingest \
  -H "Authorization: Bearer $TRACKMCP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"events":[{
    "event_id":"unique-id",
    "event_type":"tool_call",
    "service":"my-mcp-server",
    "environment":"production",
    "tool_name":"search",
    "started_at":"2026-01-01T00:00:00Z",
    "duration_ms":42,
    "success":true,
    "is_error":false,
    "payload":{"args":{}}
  }]}'

Endpoints

MethodEndpoint

POST/api/v1/ingestSubmit a validated telemetry batch

GET/api/v1/analytics?days=30Workspace metrics, tools, clients, sessions, and insights

GET/api/v1/traces?session_id=...Inspect the ordered events for one session

Example analytics response

Analytics responses are JSON. The days query parameter accepts 1-90 days and defaults to 30.

{
  "range_days": 7,
  "tool_calls": 14208,
  "sessions": 3120,
  "errors": 412,
  "completion_rate": 0.75,
  "tools": [{ "name": "search_docs", "calls": 14208, "error_rate": 0.002 }],
  "insights": []
}