MCP: whoami, and Motor Block usage

October 20, 2026

New tool: motorical_whoami. An agent can now ask who it is acting for instead of guessing. It returns the account (id, owner email, name), the plan, and, over OAuth, the permissions the connection holds, the Motor Blocks it covers and the permissions that could still be added, with the page where you add them. The Public API route is GET /api/public/v1/account/whoami.
Motor Block usage shows real numbers. The daily, hourly and burst usage of a single Motor Block (dashboard, GET /motor-blocks/{id}/rate-limits and the overview) used to read 0 whatever you had sent. It now matches what was actually sent. Account-level usage was already correct.
Cleaner tool list over OAuth. The two 6-digit-code allowlist tools, which only ever worked from a dashboard session, are no longer listed to an OAuth connection; use motorical_free_recipient_add there. Domain tool descriptions now state the scope they need. motorical_get_logs documents its query terms (code: and id:).

If you use the local server, update to @motorical/mcp 1.13.0.