Step-by-step observability for MCP agent workflows
Step-by-step observability for MCP agent workflows
Local-first, MCP-native observability for agent workflows. Every tool call, prompt transformation, latency, and token count is recorded in a local SQLite database — no cloud account, no API key, no traces leaving your machine. Built specifically for MCP rather than bolted onto a generic LLM proxy.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| trace_start | begin a new trace; returns a trace_id for subsequent calls |
| trace_step | record one tool call step (inputs, outputs, optional token count and latency) |
| trace_end | mark a trace as completed |
| list_traces | list stored traces with names, statuses, and timestamps |
| get_trace_summary | token totals, step count, latency, and cost estimate for a trace |
| compare_traces | diff two traces side by side (step counts, tokens, latency) |
| extract_reasoning_chain | extract only reasoning/thinking steps from a trace |
| export_dashboard | generate a self-contained single-file HTML dashboard with latency waterfall |
| export_otel | export one or all traces in OpenTelemetry OTLP JSON span format |
| export_compliance_log | export the compliance audit log as JSON or CSV, with optional date range filtering |
| configure_alerts | configure alert rules on latency, error rate, or cost; fire to Slack or generic webhooks |
| set_retention_policy | set how many days to keep traces (in-memory; must be called before apply_retention) |
| apply_retention | archive traces older than the configured threshold; delete traces past 2x the threshold |
{
"mcpServers": {
"trace-inspector": {
"command": "npx",
"args": ["-y", "mcp-agent-trace-inspector@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Connect Flutter applications with AI coding assistants via the Model Context Protocol.
Enables natural language interaction with Splunk Enterprise and Cloud for searching data and managing resources.