MCP

Drive Busymate from your AI client

The busymate-net MCP server exposes 87 JSON-RPC tools that mirror every dashboard read and write — connect Claude, Cursor, or any MCP client over OAuth 2.1.

Read the docs

MCP · busymate

Connected OAuth 2.187 tools

inspect_requestsget_statslist_devicesget_statuslist_entriesset_settingscreate_tabsend_pushlist_roleslink_telegram+77 more…

Add to Claude Code

bash

# Claude Code — add the server, then authorize in your browser:
claude mcp add --transport http busymate-net https://mcp.busymate.net

Or any MCP client — config

json

{
  "mcpServers": {
    "busymate-net": {
      "url": "https://mcp.busymate.net"
    }
  }
}

Why MCP

Your tools, your data, your assistant

Everything you can do in the dashboard, an MCP client can do on your behalf — scoped to your role and gated on confirmation for anything destructive.

87 JSON-RPC tools

Full dashboard parity — devices, entries, settings, service groups, tags, stats, infra status, workspaces, snapshots, roles, and more, all callable as MCP tools.

OAuth 2.1, no pasted tokens

Clients register dynamically (DCR) and authenticate with PKCE — the same OAuth token authenticates MCP, REST, and Realtime. No universal token to leak.

Works with any MCP client

Point Claude, Cursor, or any Model Context Protocol client at the endpoint and the tools appear — confirm-gated for every destructive action.

Connect your MCP client

Follow the Connect guide in the docs to register your client and authorize it over OAuth — then call any of the 87 tools.

Read the docs Open the dashboard