Skip to main content

MCP: onboarding state needs read:domains

Motorical
  • Fixed. motorical_get_onboarding_state was listed on the analytics server under read:analytics, but the API route behind it needs 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.
  • Now. The tool needs read:domains (which carries config.read) and is listed on the domains server and main. A connection without a domains read no longer sees it, instead of seeing it and being refused. Nothing that worked before is lost: the tool never worked for the connections affected.
  • Why not every connection. Unlike motorical_whoami, it reports domain verification, DNS readiness and Motor Block state, which an agent that only sends or only reads analytics has no reason to enumerate.
  • A check keeps scopes honest. The documentation build now compares every MCP tool's scope with the scope its API route requires; these two tools were the only mismatches.
  • Packages. @motorical/mcp 1.22.0 and @motorical/scope-catalog 0.7.0 are on npm; the hosted servers already run the change.

Documentation changed

Tags:
Last updated on