Workflow Automation · Sensibo + Claude
Sensibo MCP with Claude: Automate Air Conditioning Comfort and Energy Use
The short answer
Claude works with Sensibo through the Model Context Protocol (MCP), a secure standard that lets Claude read climate data and make approved changes. Using an API key, Claude can check room temperatures, adjust air conditioners and schedule routines, all within permissions your organisation sets.
What is Sensibo?
Sensibo is a smart controller platform for air conditioners and heat pumps. It adds Wi-Fi connectivity and automation to existing units, so they can be managed remotely from a phone or computer. Facilities teams, property managers, hospitality operators and office administrators use it to keep spaces comfortable while reducing wasted energy when rooms are empty.
How Claude connects to Sensibo through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. For Sensibo, the connection is made with an API key, so access is tied to a specific account that you can review or revoke at any time.
Once connected, Claude can typically read the current and historical readings from each room, check whether units are on or off, and review schedules. It can also suggest or make adjustments such as changing a set temperature, switching modes or turning a unit off after hours, all in response to plain-language instructions from your team.
Permissions and approvals keep people in charge. We configure access with least-privilege settings so Claude only sees the devices it needs. Consequential actions, such as changing settings across a whole building, can require a person to approve first, and every action is recorded in an audit log.
What you can automate
Monitoring indoor climate across sites
A facilities manager asks Claude for a summary of temperature and humidity across all offices each morning. Claude reads the latest readings from each Sensibo-controlled room and flags any space outside the comfort range, so the team can respond before staff complain. This replaces walking floors or checking several apps.
Scheduling air conditioning around occupancy
Office administrators can describe their working patterns in plain words, such as cooling meeting rooms only on booked days. Claude reviews the calendars or booking data and proposes AC routines for each room. Once approved, the schedules run automatically, which can reduce cooling costs in rooms that sit empty.
Responding to guest comfort requests
In hotels and serviced apartments, a guest service team can receive a request that a room is too warm. Claude checks the current reading in that room, makes an approved adjustment to the set temperature and confirms the change back to the team. Requests are handled quickly without a technician visiting the room.
Reporting energy-related usage patterns
Property managers often need evidence of how their systems run. Claude can review operating hours and schedule history for selected units and produce a plain summary of when cooling ran and where routines could be tightened. This gives leaders a clear basis for decisions about settings and maintenance.
Pre-conditioning spaces before events
A events or training coordinator can ask Claude to cool a hall an hour before a session starts. Claude checks the room's current state, sets the routine and notifies the coordinator once it is in place. This keeps attendees comfortable without someone manually adjusting units before each event.
An end-to-end workflow: Booking-led cooling for meeting rooms
TriggerA meeting room is booked in Microsoft 365 Outlook for a session starting within the next hour.
Claude reads the booking details from the room calendar in Microsoft 365.
Claude checks the current temperature in that room through Sensibo.
If the room is outside the comfort range, Claude proposes a cooling routine and sends it to the facilities team for approval.
Once approved, Claude activates the Sensibo routine so the room is comfortable when the meeting starts.
When the booking ends, Claude switches the unit off or returns it to an energy-saving setting and records the action in the log.
OutcomeMeeting rooms are comfortable when people arrive and are not cooled when empty, which typically reduces wasted energy and avoids complaints. Facilities staff keep control through approvals and a full audit trail.
How we set it up
Book a free automation audit
We review how your team manages air conditioning today and identify the workflows worth automating, such as scheduling, monitoring or guest requests.
Confirm access and scope
We agree which sites, rooms and units Claude should see. Sensibo is connected using an API key tied to your account, configured with least-privilege access.
Connect Claude through MCP
We set up the MCP connection so Claude can read climate data and make approved changes in Sensibo, and link it to your other systems such as Microsoft 365 or your ticketing tool.
Design, test and approve
We build the workflow, test it against real past cases and define which actions need human approval before any change is made.
Launch, monitor and train
We go live with monitoring and audit logs, then train your facilities, administration and guest service teams to use the workflow confidently.
Who benefits
- Facilities managers
- Monitor climate across many sites from one conversation and act on problems before they are reported.
- Office and workplace administrators
- Align cooling with bookings and working hours without manual adjustments.
- Hotel and hospitality operations teams
- Respond to guest comfort requests quickly and consistently.
- Property owners and finance leaders
- Gain clear summaries of how climate systems run and where settings can be improved.
Security and control
- Access is limited to the specific devices and actions each workflow needs, using least-privilege settings.
- Consequential changes, such as adjusting many rooms at once, can require approval from a named person.
- Every action Claude takes is recorded in an audit log that your team can review.
- The API key is stored securely and can be rotated or revoked at any time.
- Workflows are tested against real cases before launch and monitored afterwards.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host their Claude workflows in the US, UK or European Union to align with local data expectations. In India, we configure workflows to meet the Digital Personal Data Protection Act, 2023, with hosting in India where required. For organisations in the UAE and Saudi Arabia, we design around local data protection laws and select a hosting region that meets those requirements. The right region is always chosen based on your obligations.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Sensibo MCP server do?
The Sensibo MCP server acts as a secure bridge between Claude and your Sensibo account. It lets Claude read climate readings and device status and, where permitted, make changes such as adjusting temperature or switching a unit on or off. The server works within the access you grant, so Claude can only use the functions your setup allows.
Is connecting Claude to Sensibo secure?
Security depends on how the connection is configured. We use an API key tied to your account, apply least-privilege access so Claude sees only what it needs, and require approval for significant changes. Every action is logged, and the key can be rotated or revoked at any time.
What can Claude do with Sensibo once connected?
Typically, Claude can check the current and past readings from your rooms, review schedules and unit status, and make approved adjustments such as changing set temperatures or activating routines. You give instructions in plain language, and Claude carries them out within the permissions you have set.
How long does setup take?
A typical setup takes a few weeks, depending on the number of sites and units and how many workflows you want. The free automation audit comes first, followed by access setup, testing against real cases, launch and team training. We can start with one site to prove the approach before expanding.
Which account or permissions are needed?
You need an active Sensibo account with the devices you want to manage, and an API key generated from that account. In general, the key should be limited to the access your workflows require. We confirm the exact requirements during the audit so nothing is set up beyond what is needed.