Overview

The developer surface — one OAuth token, every way in: MCP, REST, Realtime, and the federation broker. The same /api section you see in the dashboard.

The developer surface for Busymate DevTools — read and write your data, subscribe to live changes, drive the assistant, and federate sign-in, all with a single OAuth access token. This is the same API section you see in the dashboard at /api, mirrored here as docs.

Busymate's backend is a standard, fully-documented API surface. There's one credential and several ways in — pick whichever fits your integration:

one OAuth tokenyour clientMCP — mcp.busymate.devREST — /rest/v1Realtime — /realtime/v1LTP — local routingFederation — SSO brokerSupabaseapi.busymate.net

One token, every surface

Everything in this section authenticates with the same OAuth 2.1 access token. There is no second key, no per-service token — the one token authenticates MCP, REST, Realtime, and the BusyBro ask API alike.

How you get one:

  • External clients run the OAuth 2.1 flow (Dynamic Client Registration + PKCE) against the MCP server — see MCP → Connect.
  • In the dashboard, your logged-in session is exchanged for the identical token automatically.

The token carries your identity and role. Every surface enforces row-level security + capabilities server-side, so a request only ever returns or changes what your role permits — see Roles & permissions.

The sub-sections

Like the dashboard's /api explorer, this section groups every integration surface side by side:

SurfaceBaseUse it for
MCPhttps://mcp.busymate.devAgent-friendly JSON-RPC tools covering every dashboard read/write (mcp.busymate.net dual-serves the same server forever).
RESThttps://api.busymate.net/rest/v1/Read/write tables and call RPCs over PostgREST.
Realtime (WS)wss://api.busymate.net/realtime/v1Subscribe to the capture firehose, device control, and table-level changes.
LTPin-processThe local analogue of MCP — how a tool routes LOCAL / REMOTE / HANDOFF per environment.
Federation (SSO)brokerAuto-log an external app's user into Busymate DevTools, takeover-safe.

Also in this section