Version
WRITE

set_resource_standby_mirror

Switch the live mirror into a resource's standby on or off, so a failover lands members in a channel that already holds the content.

When on, every post made in the channel is copied into the standby as it is made. Only a channel can be mirrored (a group cannot), the resource must keep a standby, switching on needs the Growth plan, and only the project owner may do it. Returns the standby as it now stands. The REST twin is PATCH /v1/projects/{project}/resources/{resource}/standby.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Idempotent

Sending the same arguments twice changes nothing the second time.

Arguments

resource_id*string

UUID of the resource whose standby to mirror into.

mirror*boolean

True to copy every post into the standby as it is made, false to stop.

What it returns

{  "data": {    "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",    "mirror_enabled": true,    "health_status": "healthy",    "health_status_label": "Healthy",    "health_reason": null,    "health_checked_at": "2026-09-12T02:00:00Z",    "last_mirrored_at": "2026-09-12T01:45:12Z",    "linked_at": "2026-09-01T14:22:09Z"  },  "meta": {}}

How it fails

VALIDATION_FAILED

a group, no standby, the plan lacks the prevention features, or the token is not the project owner's.

RESOURCE_NOT_FOUND

resource_id is not a resource the token can see.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks project-recovery:update.

How is this guide?

Last updated on