request_resource_standby
Ask the creator, through the connector, to pick the chat that becomes the standby for one resource. Nothing is linked by the call itself.
Linking a standby is a conversation with the creator on the connector: the bot messages them with a picker, and the standby is linked the moment they choose. The API cannot name the chat directly (that would take a platform identifier), so it starts the conversation. Needs the Growth plan and the project owner. Take an unanswered request back with withdraw_resource_standby_request. The REST twin is POST /v1/projects/{project}/resources/{resource}/standby/request.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Arguments
resource_id*stringUUID of the resource that should get a standby.
What it returns
{ "data": { "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6", "status": "request_sent" }, "meta": {}}How it fails
VALIDATION_FAILEDthe resource is a perk rather than a place, the creator cannot be reached on the connector, the plan lacks the prevention features, or the token is not the project owner's.
RESOURCE_NOT_FOUNDresource_id is not a resource the token can see.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project-recovery:create.
How is this guide?
Last updated on
request_resource_replacement
Ask the creator, through the connector, to pick the chat that replaces a resource's; the swap runs the moment they choose. Nothing is swapped by the call itself.
revert_recovery_operation
Undo a completed Disaster Recovery inside its window — a swapped channel put back, or the previous sign-in account restored.