A network debugger built for how software ships now

Busymate DevTools decrypts and captures HTTPS traffic from a real iPhone or Android device, from Chrome via DevTools Protocol, or from a farm of real phones, and streams every request and response into one live dashboard. It works like the desktop MITM proxies developers already know — but the device is real, the capture is on-device, and every entry lands in a private cloud workspace instead of staying local to one machine.

Besides the dashboard, the same data is reachable over a REST API, a realtime WebSocket feed, and an MCP (Model Context Protocol) server — so a script, a CI job, or an AI coding assistant can read and act on captures with the same access a person has in the UI.

A mobile app's traffic today is rarely one machine's problem: a bug shows up on one tester's iPhone, needs reproducing on Android, and needs sharing with a teammate who wasn't at the desk when it happened. Point-in-time, single-device capture tools make that handoff manual — export a file, paste a screenshot, describe what you saw.

Busymate brings captures into a live feed. Teammates see traffic from devices they own or have been granted access to; joining a workspace does not itself grant access to its traffic. Share a request link with an authorized teammate, or connect an AI agent with the same scoped access to inspect and replay requests.

The dashboard, the REST/WebSocket APIs, and the MCP server all read and write the same Postgres database in real time, gated by row-level security so the same role limits hold on every surface. There is no separate, weaker API tier — an AI agent connected over MCP sees exactly what a signed-in teammate's role allows, nothing more.

As of this page, that surface is 459 MCP tools covering device, capture, settings, and workspace operations — kept in lockstep with the dashboard, REST, and WebSocket surfaces on every change.