Integration

Sensibo integration

Sensibo makes smart controllers for air conditioners and heat pumps. Through its API an agent can list the account's devices, read their current AC state, sensor measurements, historical measurements and event history, turn an AC on or off or change its mode, fan, temperature or swing, set a one-off timer, manage weekly schedules and the Climate React automation, and read door sensor open and close events. Airbend organization accounts (commercial) also get organization-wide device lists, bulk AC control, bulk event and measurement reads, bulk device reset and member management. Authentication is a per-account API key created at home.sensibo.com/me/api and sent as the apiKey query parameter; Sensibo's OAuth2 (for commercial partners on request) is not used. Requests are rate limited (HTTP 429).

Connect Sensibo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Sensibo.Built from the 28 Sensibo tools below, on the connection you add once.

What you can do with Sensibo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Schedule, 5 operations

create_scheduleCreate schedulePOSTCreates a schedule that applies an AC state to the device at a local time of day, once or on recurring weekdays.
delete_scheduleDelete scheduleDELETEDeletes one schedule of the device.
enable_scheduleEnable schedulePUTEnables or disables one schedule of the device; its time, days and AC state are kept.
get_scheduleGet scheduleGETReturns one schedule of the device: time of day, timezone, recurring days, enabled flag and the AC state it applies.
list_schedulesList schedulesGETLists the device's schedules: time of day, timezone, recurring days, enabled flag and the AC state each applies. Use the id with get_schedule, enable_schedule or delete_schedule.

Ac state, 3 operations

list_ac_statesList ac statesGETReturns the device's current AC state followed by previous states, newest first (result[0].acState is the current one). limit sets how many, at most 20.
set_ac_stateSet ac statePOSTSends a full AC state to the device (power, mode, fan level, target temperature, swing); the AC switches at once. result.status reads Success when the device applied it. To change one property only, use set_ac_state_property.
set_ac_state_propertySet ac state propertyPATCHChanges a single property of the device's AC state (for example on, targetTemperature, mode, fanLevel, swing) and leaves the others as they are; the AC switches at once.

Climate react, 3 operations

configure_climate_reactConfigure climate reactPOSTSets the device's Climate React configuration: the low and high thresholds and the AC state to apply when each is crossed, and whether it is enabled. Once enabled, Sensibo switches the AC on its own.
enable_climate_reactEnable climate reactPUTTurns the device's Climate React automation on or off, keeping its configured thresholds and states.
get_climate_reactGet climate reactGETReturns the device's Climate React settings: whether it is enabled, the low and high thresholds and the AC state applied when each is crossed.

Timer, 3 operations

delete_timerDelete timerDELETEDeletes the device's active timer, so the AC state it would have applied is not applied.
get_timerGet timerGETReturns the device's active timer (the AC state it will apply), if one is set.
set_timerSet timerPUTSets a one-off timer that applies an AC state to the device in minutesFromNow minutes, replacing any timer already set.

Device, 2 operations

get_deviceGet deviceGETReturns one device's details. Pass fields (for example id,room,acState,measurements) to get its room, current AC state and latest temperature and humidity.
list_devicesList devicesGETLists every Sensibo device on the account. Pass fields (for example id,room,acState,measurements) to get each device's room, AC state and readings; use the returned id as device_id in the other tools.

Organization device, 2 operations

list_organization_devicesList organization devicesGETAirbend organizations only: lists every device of the caller's organization with room, tags, model, AC state, location name, latest readings, monthly AC usage, filter cleaning counters, policies and sensors.
reset_organization_devicesReset organization devicesPOSTAirbend organization admins only: resets several devices, clearing their settings, timers, room assignments and user associations. Not reversible through the API. Returns the ids reset and an error per device that failed.

Organization user, 2 operations

list_organization_usersList organization usersGETAirbend organization admins only: lists the organization's users with name, email, creation date and permissions (admin, device control, report access).
remove_organization_userRemove organization userDELETEAirbend organization admins only: removes a user from the organization. An admin cannot remove themselves.

Device event, 1 operation

list_device_eventsList device eventsGETReturns the device's events over the last days (default 1): AC state changes, schedule and Climate React changes, geofence, motion, Pure Boost and door events. event_id ranges: 1000000s device, 2000000s location, 3000000s user.

Door sensor event, 1 operation

list_door_sensor_eventsList door sensor eventsGETReturns the open and close events a door sensor detected over the last days (default 1), each with its timestamp.

Historical measurement, 1 operation

get_historical_measurementsGet historical measurementsGETReturns the device's temperature and humidity history over the last days (default 1).

Organization ac state, 1 operation

set_organization_ac_statesSet organization ac statesPOSTAirbend organizations only: applies one AC state to several organization devices at once (Sensibo creates a task per device). Returns the device ids scheduled and an error per device that failed.

Organization door sensor event, 1 operation

list_organization_door_sensor_eventsList organization door sensor eventsGETAirbend organizations only: returns open and close events of every door sensor in the organization over the last minutes (default 60), grouped by sensor id.

Organization event, 1 operation

list_organization_eventsList organization eventsGETAirbend organizations only: returns device events (state changes, connections and so on) of every organization device over the last minutes (default 60).

Organization measurement, 1 operation

list_organization_historical_measurementsList organization historical measurementsGETAirbend organizations only: returns sensor measurements of every organization device over the last minutes (default 60), grouped by device id, then by measurement type.

Organization user permission, 1 operation

get_organization_user_permissionsGet organization user permissionsGETAirbend organizations only: returns one user's permissions in the organization: admin, device control and report access.

Use Sensibo from Claude Code, Cursor or Codex

Connect Sensibo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Sensibo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Sensibo

Create your workspace
Sign up free. Nothing to install.
Connect Sensibo once
Add your Sensibo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.