telemetry-iter-mcp

An MCP that exposes telemetry.db (the jazz_telemetry store) via an iterator pattern — the disciplined consumer for the telemetry producer. Iterate, don't dump: an analyzing agent pulls controlled chunks across tool calls instead of loading thousands of rows. Reuses the note_iterator walk pattern.

Tools

- summary(filters) — counts by component/event/status, avg/max ms, slowest — without iterating. - new_iterator(filters) → get_next(n) / peek(n) / reset_iterator — stateful cursor over matching rows. Filters: component, event, status, pid, min_duration_ms, since, order:"slow", limit. - walk_run(pid) — trace one process/run in time order. - iterate.call_tree(events) + walk_depth_first() — reconstruct + depth-first walk the call tree from branch-point telemetry ({seq, kind:call|return|branch, fn}) — NoteIterator repointed at telemetry.

Config: TELEMETRY_DB (default ~/code/forge/telemetry.db). Read-only.