> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibrai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update

> Check for and apply self-updates to the Vibrai CLI, MCP server, Max-for-Live device, and Python remote script. Scope: swaps the CLI binary and (when the release ships them) the MCP server binary and Claude Desktop extension bundle, and reinstalls the M4L device + Python remote script. Supports check-only, interactive/non-interactive apply, force reinstall, and rollback to the previously installed CLI + MCP binaries.

Check for and apply self-updates to the Vibrai CLI, MCP server, Max-for-Live device, and Python remote script. Scope: swaps the CLI binary and (when the release ships them) the MCP server binary and Claude Desktop extension bundle, and reinstalls the M4L device + Python remote script. Supports check-only, interactive/non-interactive apply, force reinstall, and rollback to the previously installed CLI + MCP binaries.

## Command line

### `update`

Check for and install the latest Vibrai release (CLI + MCP server + M4L device + Python remote script)

```bash theme={null}
vibrai update --check --yes --force --rollback
```

<ParamField path="--check">
  Only report whether an update is available; make no changes.
</ParamField>

<ParamField path="--yes">
  Apply without the confirmation prompt (required for non-interactive use).
</ParamField>

<ParamField path="--force">
  Reinstall the latest release even if already up to date.
</ParamField>

<ParamField path="--rollback">
  Restore the previously installed CLI binary (and MCP server binary, if present) from backup.
</ParamField>

## MCP tools

### `update`

Check for and optionally install the latest Vibrai release. By default (apply=false) this only reports whether an update is available. Pass apply=true to download + verify (SHA-256) + swap the vibrai CLI binary, swap the MCP server binary (Vibrai.Mcp) and refresh the Claude Desktop extension bundle (Vibrai.mcpb) when the release ships them, and reinstall the Max-for-Live device + Python remote script (via the same installer as install\_device / install\_vibrai\_remote\_script). If Ableton Live is running during an apply, M4L/Python changes take effect after you restart Live; if the MCP server was updated, restart Claude Desktop (or your MCP client) to use the new version. Returns the current/latest version, update\_available, per-component status (cli, and mcp on platforms that ship an MCP server), and (on apply) the actions taken. Applying is destructive (swaps binaries); requires confirm=true (parity with the CLI's `vibrai update --yes`); refuses without changing anything otherwise.

```json theme={null}
{
  "tool": "update",
  "arguments": {
    "apply": "<Boolean>",
    "force": "<Boolean>",
    "rollback": "<Boolean>",
    "confirm": "<Boolean>"
  }
}
```

<ParamField path="apply" type="Boolean">
  Apply the update (download + swap + reinstall). Default false = check only.
</ParamField>

<ParamField path="force" type="Boolean">
  Reinstall even if already up to date (default false).
</ParamField>

<ParamField path="rollback" type="Boolean">
  Roll back to the previously installed CLI binary and MCP server binary, if present (default false).
</ParamField>

<ParamField path="confirm" type="Boolean">
  Confirm the binary swap (CLI --yes equivalent). Must be true when apply=true; confirm with the user first.
</ParamField>