@opentrain-ai/mcp 0.5.2 or later and on the hosted endpoint at https://app.opentrain.ai/mcp.
All tools follow the Project To-dos safety contract: explicit audiences, strict SELECTED validation, signed preflight receipts for broad assignments, and request-bound idempotency.
The configured account must have the default-off Project To-dos agent surface
enabled. A full-access key supplies the scopes below but does not bypass that
account gate; AGENT_SURFACE_DISABLED is an enablement error, not a reason to
rotate the key.
Tools
Safety behavior
create_itemandassignrefuse to run without an explicitaudience— in the focused tools and in both generic unions — before any request is sent. OpenTrain never defaults to all active workers.- The generic unions cannot bypass recipient preview: fan-out and quiz-assignment bodies are redirected to the focused preflight-then-mutate tools.
- Receipts are minted by the preflight tools, live about 15 minutes, and die early if the roster or the exact payload changes.
- Retries with the same
idempotencyKeyconverge; a replay reports itself and never widens the original fan-out.update_itemis the exception — it publishes a new immutable version per call and must not be blind-retried.
Permissions
Reads requireproject_todos:read; every mutation requires project_todos:write and a claimed account. See Scopes and capabilities, the API reference, and the quiz surface.