Agents Index

Busymate DevTools

Online

Capture, inspect & debug HTTPS traffic across iOS, Android, browsers & backends — 304 MCP tools.

Visit publisherConnectJSON

What it can do: 53 tools

  • get_product_pricing read-onlyReturn the canonical Busymate DevTools plan prices and cloud phone/browser rental rates, with numeric amounts, USD currency, billing periods and https://busymate.dev/pricing as the source. Check draft, publicationStatus
  • search_docs read-onlySearch the public Busymate DevTools documentation (setup and how-to guides for iPhone/iPad, Android, Mac/Windows/Linux browsers and desktop apps, the dashboard, proxy, bmc CLI, MCP and API) and return the best-matching p
  • read_docs_page read-onlyReturn the full markdown of one public Busymate DevTools documentation page with its https://docs.busymate.dev URL. Pass the slug from search_docs or list_docs_sections, e.g. "android/install". Unknown or non-public slug
  • list_docs_sections read-onlyReturn the public Busymate DevTools documentation's table of contents: every section and its pages with title, slug, one-line description and https://docs.busymate.dev URL. Public read; no sign-in or account data.
  • get_setup_steps read-onlyReturn the official step-by-step guide for setting up devices with Busymate DevTools: account, install, sign in to pair, trust the certificate, start capture and check it works. Pass platform (iphone, ipad, ios, android,
  • list_breakpoint_events read-onlyList HELD (paused) breakpoint exchanges — the READ side of the breakpoint-continue flow (public.breakpoint_events; a row with resumed_at NULL is a request/response the proxy is holding RIGHT NOW, waiting for breakpoint_c
  • get_device read-onlyGet one device row by uuid, name, OR its PAC PORT — the DIRECT resolver for a KNOWN device: when you already hold a device uuid/name (from traffic rows, audit events, another tool's result) or a per-device PAC/proxy endp
  • list_devices read-onlyList devices, ONE PAGE at a time — YOUR OWN by default (owner-scoped to the calling account: the same reach the dashboard gives you), or the WHOLE fleet with `all:true` (devices:view operators only; re-verified server-si
  • get_device_status read-onlyGet a device's live status: `online` is DERIVED truth (#776 — devices.last_seen_at within 90s, 150s for farm hosts; the same derivation as every other surface, so it can't latch stale), plus the device_status row (last_h
  • get_device_health read-onlyTHE ONE QUERY (#1157/#1160): the latest capture-health projection for ONE device — one `device_health` row, no scan, no on-device access needed. Answers "is the TLS-intercept engine armed, and if not, WHY": engine_state
  • list_device_events read-onlyThe MULTI-PRODUCER device TELEMETRY event stream (#1160/#1208) — every DECISION and STATE TRANSITION reported about the capture pipeline by the iOS app OR by the PAC/proxy server (public.device_events, 14-day retention,
  • list_device_audit_modes read-onlyEvery device with AUDIT-mode telemetry currently armed — device_uuid + name, enabled, expires_at + expires_in, level, categories, who armed it (set_by_label) and when (set_at). The 'standing cost is never invisible' list
  • test_pac_connection read-onlyPROVE whether PAC capture actually works for ONE device — the "is it really working?" answer, not "does it look configured". Runs 8 independent checks and returns a per-check verdict with a specific human fix: (1) connec
  • list_screen_share_recordings read-onlyList saved screen-share RECORDINGS (#1916) — operator-captured mp4s of live share streams (the dashboard viewer's Record control), saved for later reference in public.screen_share_recordings. YOUR OWN recordings by defau
  • get_screen_share_recording read-onlyFetch ONE saved screen-share recording (#1916) by id — the metadata row plus, with `with_url:true`, a SHORT-TTL (600s) signed playback URL + a download URL for the mp4 (H.264 — plays in any <video> element / on iPhone).
  • get_my_account read-onlyYOUR account at a glance — ONE self-scoped read returning the calling account's profile (name, display_name, email, role, sign-in providers, user_id, created_at), your per-user default connection type (own value + the gl
  • get_device_egress_status read-onlyRead a device's egress-IP set (#1432) — the device→proxy INGRESS / CONNECT-source ADMISSION IPs the proxy allowlists for it (the addresses it will ACCEPT this device's CONNECTs FROM), PLUS any manual dev overrides. These
  • get_device_egress_fail_posture read-onlyRead a device's PAC egress FAIL POSTURE (#1657) — what the proxy does when the device is handed the #76 PAC DIRECT fallback (its PAC-fetch source IP is not yet in the CONNECT-source admission allowlist, routine on CGNAT)
  • get_entry_count read-onlyCount entries in a workspace (workspace_id or workspace_slug) with optional device/host/method/status/search filters.
  • list_wipe_jobs read-onlyList the workspace's WIPE JOBS (public.entries_wipe_jobs, #2147) — the ONE source of truth for wipe progress, the same rows the dashboard's wipe banner renders. Each job: the EXACT device set, the narrowing predicate (ho
  • get_entry_counts_freshness read-onlyThe ONE freshness surface for every dashboard counter (#2147): mode 'live' — entry_dh_counts is a LEDGER maintained in the write transaction of every insert / delete / wipe / partition drop and broadcast as COUNTS_DELTA
  • search_entries read-onlyLOCATE captured entries by ANY keyword `q` — matched against the host/url/path AND the DECRYPTED request/response DATA: the request+response HEADERS and the request+response BODY text (#1577). Case-insensitive substring.
  • list_entries read-onlyLIST the newest captured traffic entries as SLIM feed rows (id, ts, device, kind, request_id, host, path, method, status, contentType, url — NO bodies/headers) — the dashboard main live feed's MCP-parity read (#778). No
  • get_entry read-onlyGet ONE captured entry's FULL detail by the id you already hold — method, URL, host, path, status, timing (duration_ms) + sizes, the request AND response HEADERS, and the request AND response BODIES (size-capped, truncat
  • export_har read-onlyExport captured entries as a HAR 1.2 log. Optionally scope by device, host, and date range.
  • inspect_requests read-onlyDeep-inspect FULL captured request/response detail for ONE host — method, URL, request + response HEADERS, and request + response BODIES (size-capped). The tool for reverse-engineering how a real app/API works from its a
  • summarize_device_traffic read-onlyBOUNDED traffic aggregation for ONE device — the FIRST tool to call to report what a device is doing, find the busy/flooding host, or pick a host to clean up. REQUIRES a device (`device_uuid` or `deviceName`) — a host al
  • list_service_groups read-onlyList every service group (full rows incl. ssl_proxy_domains) with each group's primary_agent + ordered agents[] from the service_group_agents join.
  • get_service_group read-onlyGet one service group by id or name.
  • list_tags read-onlyList every tag (id, name, color, patterns).
  • get_device_settings read-onlyRead settings_device for one device (device_uuid or deviceName).
  • get_subscription read-onlyReturn the caller's OWN Stripe subscription(s) — status/price/product/quantity/period/trial/cancel-at-period-end (from stripe_subscriptions, owner-scoped to the caller's OAuth sub). A billing:view operator (admin via gra
  • list_invoices read-onlyList the caller's OWN Stripe invoices — status/amounts (minor units)/currency/hosted_invoice_url/period (from stripe_invoices, owner-scoped to the caller's OAuth sub), newest first. Optional `limit` (default 50, max 200)
  • get_usage read-onlyReturn the caller's OWN metered usage rollup (metric `captured_entries` = count of captured entries per device per period; from stripe_usage_events, owner-scoped to the caller's OAuth sub) aggregated by period over a win
  • get_block_rules_device read-onlyRead what ONE device ENFORCES — the EFFECTIVE 4-tier block-rule union (global ++ service ++ user ++ device, de-duped by id, device wins then user then service then global) plus the SERVICE list (the applied service group
  • list_todos read-onlyList YOUR to-dos from the /todo app (public.todos) — the shared "what to do / what's done" list you + the user both maintain. Owner-scoped to the calling account. Filters: `status` (open|in_progress|done|blocked), `prior
  • get_todo read-onlyGet ONE of YOUR to-dos by id — its full row. Owner-scoped: an id you don't own returns not-found (never reveals another user's to-do). Returns { todo }.
  • list_advisor_findings read-onlyBrowse the ADVISOR CENTER findings (public.advisor_findings) — the advisor-monitor's deduped audit/health findings you see on the dashboard /advisor view. Filter by `severity` (info|warning|alert), `kind` (a taxonomy slu
  • get_advisor_finding read-onlyGet ONE advisor finding in FULL by its `fingerprint` (from list_advisor_findings) — with its up-to-20 resolved (already-redacted) audit EVENTS, the SCOPED /audit deep link, and the /advisor permalink, so you can act with
  • share_advisor_finding read-onlyBuild a SHAREABLE package for ONE advisor finding — the max-context markdown + flat LLM prose + the permalink, so it can be dropped into a doc/chat/issue with full context (Finding · Analysis · Evidence · Deep links · Re

…and 13 more.

Connect it

Claude Code
claude mcp add --transport http busymate-devtools https://mcp.busymate.dev
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.busymate.dev
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "busymate-devtools": {
      "url": "https://mcp.busymate.dev"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "busymate-devtools": {
      "type": "http",
      "url": "https://mcp.busymate.dev"
    }
  }
}

Questions

What does Busymate DevTools do?

Capture, inspect & debug HTTPS traffic across iOS, Android, browsers & backends — 304 MCP tools. It exposes 53 tools to AI assistants.

What tools does Busymate DevTools provide?

53 tools, including get_product_pricing, search_docs, read_docs_page, list_docs_sections, get_setup_steps, list_breakpoint_events, get_device, list_devices, get_device_status, get_device_health, list_device_events, list_device_audit_modes….

How do I connect Busymate DevTools to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.busymate.dev as a custom connector or MCP server. Copy-paste setup is on this page.

Does Busymate DevTools require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Busymate DevTools online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Busymate DevTools?

busymate.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Developer Tools