405 tools. One URL. Your whole stack, agent-ready.
Point Claude, Cursor, or any MCP client at mcp.busymate.dev and drive everything the dashboard can do — capture, devices, browsers, phone farms — over standard JSON-RPC with OAuth 2.1.
# Claude Code — add the server, then authorize in your browser:
claude mcp add --transport http busymate-devtools https://mcp.busymate.dev{
"mcpServers": {
"busymate-devtools": {
"url": "https://mcp.busymate.dev"
}
}
}Your tools, your data, your agent
Everything you can do in the dashboard, an MCP client can do on your behalf — scoped to your role, gated on confirmation for anything destructive, and permanently audit-logged.
Full dashboard parity
Every read and write the dashboard performs has a matching tool. If a human can do it in the UI, an agent can do it over MCP — parity is a standing rule here, not a roadmap item.
Real superpowers, not CRUD
Remote Chrome control. Android and iOS farm automation with live mirroring. TestFlight beta admin. Billing. A queryable audit log. These aren't wrappers around a database — they're the platform's actual capabilities.
OAuth 2.1, done right
Dynamic client registration plus PKCE — no pasted API keys. The one token you get back also authenticates REST, WebSockets and Edge Functions: one identity across every surface.
Safe enough for production
Every call is scoped to the caller's role by the database itself. Destructive tools demand an explicit confirm. And everything — every tool, every agent — lands in the audit trail.
Try it before you wire it
The dashboard's in-app MCP console fires real tool calls with your own logged-in token and shows live responses. No Postman, no mock server — the actual API, right there in the app.
Related: the network-capture REST APIthe realtime traffic WebSocketthe RBAC & audit-trail model
Connect your MCP client
One click for Cursor or VS Code, or copy the config for Claude, ChatGPT, or any client — authorize over OAuth, then call any of the 405 tools.