MCP Tools — Plans
Several writes in order under one confirmation; payment steps are handed back for their own.
1 tool in this registry. Every tool is callable over the MCP endpoint (
/api/mcp); the badge on each shows which auth modes may invoke it. See Auth models and the MCP overview.
rivr.plans.execute
Session
MCP Token
Run several writes in order with ONE confirmation. steps is an ordered list of {id, tool, args, summary}; an arg may be {"$ref":"<earlierStepId>.<path>"} to use an earlier step's result (e.g. {"$ref":"org.resourceId"} for the id of a group created by the step with id "org"). A failed step skips only the steps that use its result through a $ref (directly or through another skipped step); every other step still runs, and each is reported as done, failed, skipped or deferred. Each step's args are checked against that tool's own input schema before the card is shown, so write them exactly to it. Steps that move money or put a price on something (wallet, payouts, priced membership plans) are never run inside a plan: they come back as follow-ups that each need their own confirm, and no step may $ref one. At most 24 steps.
Parameters
| Param | Type | Required | Description |
|---|---|---|---|
steps | object[] | yes | |
title | string | — | What the plan sets up, in a few words. |