Busymate DevTools

Your app’s traffic, explained

Capture HTTP(S) traffic from iPhone, Android, and Chrome. Inspect requests, test responses, and ask AI to help explain failures.

Four labeled capture sources — an iPhone, an Android phone, a Chrome window and a rack of phones — stream live traffic into one large Busymate dashboard of request rows with green 200 and red 500 status codes and a rising sparkline. Under the dashboard, on the same feed, a BusyBro AI chat plays out: the user asks why this 500, the recent_entries and get_entry tool checks resolve, and BusyBro answers that Stripe returned 500 on POST /v1/charges and offers resend_request. ios android chrome farm dash.busymate.dev GET 200 POST 201 GET 500 PUT 200 DEL 204 BusyBro same feed why this 500? tools ran recent_entries get_entry Stripe 500 on POST /v1/charges resend_request?

Demo

See it in real life

dash.busymate.dev

An 18-second screen recording of the live dashboard: /v1/charge requests streaming in from an iPhone, one opened to its request and response, then BusyBro asked to explain it. No mockups — this is the product as it runs.

  • Real screen recording
  • Live dashboard feed
  • BusyBro included

BusyBro

Ask the live feed. Get receipts.

BusyBro reads the HTTPS you already captured. Ask how an app logs in or why a 500 happened — it names the tools it ran, redacts secrets, and asks before it replays.

  • Same live feed
  • Tools you can see
  • Confirm-gated replay

On-device

Capture it on the phoneSee it on the phone

Decrypt only the hosts you pick. No Mac, no cable.

  • iOS VPN
  • Android TUN
  • No desktop required
Live HTTPS feed on iPhone
Live HTTPS feed on Android

One live feed

Don't just watch. Change it live

Open a request, pause it, send back a fake response — or hand the same feed to an AI.

  • Breakpoints
  • Mocks
  • JS scripts
Request detail on iPhone

MCP server

Connect the agent you already use

454 tools over MCP. Your agent inspects the same live feed and drives replay, mocking and device control — destructive actions always ask first.

  • OAuth 2.1
  • Confirm-gated
  • RBAC-scoped
Add to Claude Code
bash
# Claude Code — add the server, then authorize in your browser:
claude mcp add --transport http busymate-devtools https://mcp.busymate.dev

Capture anywhere

Every source. One feed.

Phones, Chrome, a proxy, or a rack of devices — they all land in the same live table.

HTTPS on your iPhone — no Mac needed.

HTTPS on your Android phone — no computer needed.

The live table your whole team shares.

Capture HTTP(S) from browsers and backends.

Capture Chrome with one command.

Real phones, controlled from the browser.

How it works

Three steps to a live feed

From a phone you own to a dashboard your team — and Claude — can use.

  1. Get iOS or Android, or one command for Chrome.

  2. Pick what to decrypt. Watch requests land live.

  3. Fix a response yourself, or let Claude do it.

Teammate & trust

Safe on real traffic

Share access deliberately, review activity, and keep stored credentials out of the interface.

An AI that remembers your traffic.

Scoped access, an audit trail, and a write-only secrets vault.

Your users sign in with one tap.

FAQ

Common questions

Can I capture HTTPS on an iPhone without a Mac?

Yes. The iPhone app captures on the phone itself — no Mac, no cable.

How does Android capture work without a Wi-Fi proxy?

The Android app captures on the phone. You can still use a Wi-Fi proxy for other devices if you want.

Can Claude or Cursor read my captured traffic?

Yes. Connect Claude or Cursor — they see the same live feed you do, limited to your role.

Can an AI agent run destructive actions on my devices?

Only if you confirm. Destructive actions ask first, and everything is logged. Secrets cannot be read back.

How is this different from Proxyman, Charles, HTTP Toolkit, or mitmproxy?

These tools offer different local capture, sharing, and automation workflows. Busymate combines a hosted capture feed, role-scoped access, an agent with 454 MCP tools, and real-device control. See the sourced comparisons to choose the right fit.

Is this an LLM observability or tracing platform?

No. It shows the raw HTTPS your apps (and agents) send, so you can inspect and replay. Use it next to a tracing stack, not instead of one.

Capture your first request

Choose your capture source and follow the setup guide. HTTPS decryption requires certificate trust and a supported app.

Ask your mate