Stop squinting at the DevTools Network tab. browser-flow-tracker watches a page while you navigate, filters out the noise, and hands you a clean document of every API call β with a sequence diagram.
A browser opens, you click through the real flow, then say done β or just close the window. Files are written automatically.
Every recording writes three files. The one you read is the Markdown doc.
.md flow docA readable write-up: overview, a Mermaid sequence diagram, an ordered call table, and per-call detail.
.flow.jsonStructured, ordered data with request/response bodies β for Claude/Cursor to build even richer docs.
.harStandard HAR 1.2 β open it in Chrome DevTools, Postman, Insomnia or Charles.
No Node.js, no PATH headaches. One command installs a standalone binary β on macOS, Windows or Linux.
macOS & Linux β Terminal:
curl -fsSL https://apiflowtracker.com/install.sh | sh
Windows β PowerShell:
irm https://apiflowtracker.com/install.ps1 | iex
The installer prints the exact MCP config to add to Claude/Cursor β it looks like this (macOS/Linux path shown):
{
"mcpServers": {
"browser-flow-tracker": {
"command": "/usr/local/bin/browser-flow-tracker"
}
}
}
Already have Node? You can instead use "command": "npx", "args": ["-y", "browser-flow-tracker@latest"].
It speaks the browser's own DevTools Protocol, then does the tedious parts for you.
Drops images, fonts, CSS and analytics/telemetry (PostHog, GA4, RUM) so you see only the real API calls.
Auth headers, cookies and tokens are redacted by default. Log in once β the private profile remembers you.
The capture is user-driven: it records your real, authenticated flow instead of guessing. It never clicks for you.
Works with Brave, Chrome, Arc, Edge and other Chromium browsers. Auto-picks a free debug port β no setup.