Connect Busymate DevTools to your AI agent
One URL — mcp.busymate.dev — gives Claude, Cursor, VS Code, ChatGPT, or any MCP client all 304 tools, over OAuth 2.1. No API keys, no config server — paste it once and authorize in the browser.
https://mcp.busymate.dev# Claude Code — add the server, then authorize in your browser:
claude mcp add --transport http busymate-devtools https://mcp.busymate.devPick your client
Cursor and VS Code install in a single click. For everything else, copy the config — every client points at the same URL and authorizes over OAuth the first time you use a tool.
Claude Code
Add the server from your terminal. The first tool call opens your browser to authorize.
# Claude Code — add the server, then authorize in your browser:
claude mcp add --transport http busymate-devtools https://mcp.busymate.devClaude.ai & Claude Desktop
Settings → Connectors → Add custom connector, paste the URL, click Connect, and authorize in the browser. No file to edit.
https://mcp.busymate.devCursor
One click adds it and authorizes over OAuth. Or add it by hand to ~/.cursor/mcp.json (global) or a project .cursor/mcp.json:
{
"mcpServers": {
"busymate-devtools": {
"url": "https://mcp.busymate.dev"
}
}
}VS Code (Copilot)
One click installs it into VS Code. Or add it by hand to a workspace .vscode/mcp.json (the root key is servers):
{
"servers": {
"busymate-devtools": {
"type": "http",
"url": "https://mcp.busymate.dev"
}
}
}ChatGPT
Where developer-mode connectors are available: Settings → Connectors → Add, paste the URL, and authorize. Availability varies by plan.
https://mcp.busymate.devAny other MCP client
The Streamable-HTTP transport is standard — Continue, Cline, Zed, or your own bot use the same config. Point it at the URL:
{
"mcpServers": {
"busymate-devtools": {
"url": "https://mcp.busymate.dev"
}
}
}Your account, your rules
Access is OAuth 2.1 with Dynamic Client Registration and PKCE — no pasted keys, no shared secret. The one token an agent receives authenticates every Busymate surface (MCP, REST, WebSockets, Edge Functions) and is scoped to your own role: an agent can only do what you could do in the dashboard.
- RBAC-scoped
- confirm-gated
- secrets redacted
OAuth 2.1, no keys
Dynamic client registration (RFC 7591) + PKCE (S256) + refresh rotation. Users authorize in the browser against Busymate's sign-in — there's no API key to paste or leak.
Scoped to your role
Every call is authorized by the database itself (RBAC). Destructive tools demand an explicit confirmation, and secret values are never returned — they're write-only and redacted.
Fully audit-logged
Every tool call — every agent, every action — lands in your account's audit trail, so you can always see what an agent did on your behalf.
Read more: PrivacyTermsthe RBAC & audit-trail model
What your agent can drive
Full dashboard parity — if a human can do it in the UI, an agent can do it over MCP. A few of the categories:
Capture & inspect traffic
Search, inspect, tag, export (HAR), summarize, and delete captured requests and responses — per device or across your whole fleet.
Control devices
List, rename, unpair, toggle the VPN, set a connection type, or route a device's egress through an upstream proxy.
Drive a remote browser
Raw Chrome DevTools Protocol passthrough — open, evaluate, screenshot, and snapshot a connected device's Chrome.
Automate phone farms
Android and iOS device-farm automation — tap, type, swipe, install, and manage app lifecycle, with live mirroring.
Script & shape requests
Sandboxed request/response scripts, auto-block rules, breakpoints, and paused domains — mutate or synthesize traffic in flight.
Run the platform
Roles & capabilities (RBAC), TestFlight beta admin, billing, a queryable audit trail, notifications, to-dos, workspaces, and BusyBro team memory.
Related: the MCP server overviewthe network-capture REST APIthe RBAC & audit-trail model
Connect in under a minute
Add mcp.busymate.dev to your client, authorize once in the browser, and start calling any of the 304 tools. Follow the Connect guide for the full walkthrough.