Skip to main content

MCP: motorical_whoami works for every connection

Motorical
  • Fixed. motorical_whoami was listed under read:analytics, but the API route behind it needed a different scope (config.read) that read:analytics does not carry. A connection holding only read:analytics saw the tool and got 403 missing_scope; a connection holding only send:transactional or manage:webhooks never saw it.
  • Now. Any OAuth connection can call it, whatever scopes it holds, and every hosted server except signup lists it, so an agent can always ask what it holds. It stays visible after the sandbox phase.
  • Unchanged. Every other credential (an account-key token, a dashboard token) still needs config.read to read it, because the owner email is returned in full.
  • Packages. @motorical/mcp 1.21.0 and @motorical/scope-catalog 0.6.0 are on npm; the hosted servers already run the change.

Documentation changed

Tags:
Last updated on