mcp-trace-inspector

Inspect recorded agent-run failures and approvals from local JSONL. mcp-trace-inspector is a read-only stdio MCP server for inspecting local agent-run traces, including tool failures, approval decisions, and changes between runs. It reads JSONL spans in the format described in the user guide, including traces from agent-harness.

Demo: Watch the full 48-second video · Read the reproducible story. This is a scripted regression trace, not a live-model benchmark.

The project's concrete origin was a shell-boundary regression: the harness blocked cat ../outside.txt, but the old trace recorded only that run_shell was called, not the returned diagnostic. mcp-trace-inspector and the harness now preserve and query that bounded error.

Try the included trace

git clone https://github.com/abhishekash/mcp-trace-inspector.git
cd mcp-trace-inspector
uvx --from . mcp-trace-inspector --trace-dir examples --check

--check prints JSON with the trace directory, span count, and recent run summaries, then exits. It also reports a missing directory or malformed complete JSONL record. To ask questions through MCP, connect a client using the configuration below.

Release status: The 0.3.0 GitHub release is available. The PyPI Trusted Publisher is configured; its first upload has not completed. Run the tagged Git source with uvx below until uvx mcp-trace-inspector is available. The MCP Registry entry currently lists the earlier 0.2.2 package. Publication status and directory submission handoff.

Where it fits

Use this when your agent already writes the supported JSONL span format and you want an MCP client to inspect those files without setting up a trace backend. Its focused queries include recorded approval decisions, bounded failure diagnostics, and comparisons between selected runs.

MCP Agent Trace Inspector records steps into a local SQLite database and provides a dashboard and exports. Use it when you need trace capture. This project reads trace files written by an existing producer, including agent-harness; it does not record the agent's actions itself.

For traces stored in Jaeger, Tempo, or Traceloop, use a backend-connected tool such as OpenTelemetry MCP Server. For standard OTLP traces with a local receiver, see otel-mcp. For a trace UI, instrumentation, and evaluations, see Phoenix. This project does not ingest OTLP directly or read arbitrary OpenTelemetry JSON exports; other producers may need an adapter to the documented format.

AI-native use cases

The tools read stored traces and can poll files being written, but they do not push events or infer intent from the final answer. Start with the installation and user guide, then see the real trace fixture and the tool descriptions for the query contract.

Install & run

uvx --from git+https://github.com/abhishekash/mcp-trace-inspector@v0.3.0 mcp-trace-inspector --trace-dir ./traces
# or, for local development:
git clone https://github.com/abhishekash/mcp-trace-inspector
cd mcp-trace-inspector
uvx --from . mcp-trace-inspector --trace-dir ./traces

Client configuration

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "agent-traces": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/abhishekash/mcp-trace-inspector@v0.3.0", "mcp-trace-inspector", "--trace-dir", "/path/to/traces"]
    }
  }
}

pi (~/.pi/agent/settings.json):

{
  "mcpServers": {
    "agent-traces": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/abhishekash/mcp-trace-inspector@v0.3.0", "mcp-trace-inspector", "--trace-dir", "/path/to/traces"]
    }
  }
}

agent-harness (mounted as gated tools):

harness run "Why was my last run slow?" --mcp "uvx --from git+https://github.com/abhishekash/mcp-trace-inspector@v0.3.0 mcp-trace-inspector --trace-dir ./traces"

Tools

Tool descriptions are written as prompts (when-to-use, not just what-it-does) — descriptions are the interface for agent-called tools.

Example session (real fixture trace)

> list_runs
[{ "trace_id": "f920798dd2558fcb84f9977736432a8b", "task": "Summarize the workspace's notes…",
   "tool_calls": 4, "human_decisions": 2, "stopped_reason": "completed" }]

> approval_log
[{ "tool": "write_file", "decision": "approve", "approver": "auto", … },
 { "tool": "run_shell",  "decision": "approve", "approver": "auto", … }]

Design

traces/*.jsonl ──▶ mcp_trace.core (pure query functions, zero deps)
                          │
                   mcp_trace.server (thin MCPServer adapter, mcp 2.x)
                          │
                    stdio (NDJSON JSON-RPC)

• core/server split: all logic is pure functions over parsed spans; the MCP layer only parses args and JSON-encodes results. Tests hit both layers.
• trace_id prefixes: agents fumble full 32-char hex ids; every tool accepts prefixes.
• bounded output: diagnostics are truncated and obvious credentials are redacted before query results leave the server.
• honest cost totals: token_usage returns cost_known: false and a null cost when any model span lacks a cost or marks pricing as unavailable; unknown pricing is never presented as $0.
• cursor polling: recent_activity makes the snapshot reader useful while a run is still writing spans.
• The demo fixture (examples/example_trace.jsonl) is a real agent-harness run, not hand-written.

Honest limitations

• stdio transport only (Streamable HTTP plus authenticated remote access is the next transport boundary)
• live polling re-reads snapshots; it is not a push subscription
• security audit can only report identity/provenance that the trace producer records
• read-only tools; trace mutation (annotations) is roadmap
• The Python query and server modules are available as mcp_trace; older import and command aliases remain for existing clients.

License

MIT