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

# Control displays with MCP

> Use account-scoped tools for apps, order, schedules, brightness, scenes, and firmware.

Start read-only. Ask the assistant to list displays or inspect one display before requesting a change. IDs and current version fields returned by read tools are required for several safe updates.

## Read tools

* `display_list` lists account-owned displays and online state.
* `display_get` returns settings, installed apps, policies, scenes, capabilities, and catalog references.
* `catalog_search` finds installable apps.
* `catalog_get` returns one release and its immutable configuration schema.

## Control tools

* `display_update` changes the name, day brightness, or supported panel color mapping.
* `display_set_night_schedule` configures a device-local recurring dim or off window.
* `display_set_policy` replaces the advanced display schedule.
* `installed_app_add`, `installed_app_update`, and `installed_app_reorder` manage rotation.
* `scene_create`, `scene_update`, `scene_activate`, and `scene_deactivate` manage scenes.
* `display_set_firmware_policy`, `display_install_firmware`, and `display_reflash_firmware` manage updates.

## Destructive tools

Removing an installed app or scene requires the exact confirmation value `REMOVE`. Removing a display requires `DELETE`. The server validates those values even if the MCP client also shows its own confirmation UI.

<Warning>
  `display_remove` deletes the account-owned display, its installations, pending enrollment, jobs, and Cloud credential. Use it only when the user explicitly asks to remove that exact display.
</Warning>

## Configuration boundaries

MCP can write ordinary non-secret app configuration that matches the immutable release schema. Credential and OAuth fields remain dashboard-only and are never returned to the assistant.