value
(String, optional): Target value, e.g. 50, max, min, cool, heat, red.
How to use it
value is exposed by the Aqara MCP Server MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the value tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL AQARA MCP SERVER LISTINGOther tools in Aqara MCP Server (33)
(String, required): Control action, e.g. on, off, set, up, down, warmer, cooler, start, stop.
Query all homes under the current Aqara account.
(String, required): Attribute to control, e.g. onoff, brightness, colortemperature, temperature, percentage, mode.
Query automation rule basics, filterable by automation ID, position ID, or device ID.
Query automation execution history within a time range.
(Array\<String\>, optional): Automation IDs. When provided, query prioritizes automation ID.
(String, optional): total = aggregated summary, detail = detail view.
(String, required): Query type—1 for electricity usage, 2 for electricity cost, 3 for both.
Query device basic information by room/space and device type, without real-time status.
Batch-query current firmware version and available upgrade version for devices.
Start firmware upgrades for eligible devices after filtering by device, position, or type.
(Array\<String\>, optional): Device IDs. When provided, query prioritizes device ID.
Query supported lighting effect names per device.
Query device control logs within a time range, including control time, content, and result.
Control state or attributes of specified devices, such as power, brightness, color temperature, temperature, fan speed, mode, and curtain percentage.
Query real-time device status such as power, brightness, color temperature, temperature, fan speed, and mode.
(Array\<String\>, optional): Device types, e.g. Light, Switch, Outlet, AirConditioner, WindowCovering, Camera. When empty, no device type filter is applied.
(String, required): Effect name.
Query electricity usage or cost by device, filterable by position or device, with aggregated and detailed views.
Query electricity usage or cost by home/room/space, with aggregated and detailed views.
Batch-control devices by room/space and device type—for example, “turn off all lights,” “turn off everything in the living room,” or “set all AC units to 26°.”
Query parameters required to configure lighting effects on light devices.
Apply the specified lighting effect to target devices or rooms/spaces.
Query available lighting scenarios/effects in the home.
Query basic information for all rooms/spaces in the current home.
(Array\<String\>, optional): List of room/space IDs. When empty, no position filter is applied.
(Array\<String\>, optional): Room/space IDs. When empty, queries all valid rooms.
Query scene basic information, filterable by scene ID, position ID, or device ID.
Query scene execution history within a time range.
(Array\<String\>, optional): Scene IDs. When provided, query prioritizes scene ID.
Run one or more specified scenes.
(String, optional): Granularity: 30min, 1hour, 1day, 1week, 1month.
(Array\<String\>, optional): Time interval, e.g. ["2026-01-01 00:00:00", "2026-01-01 23:59:59"].