Sensibo
Sensibo offers smart controllers that connect air conditioners and heat pumps to the internet, enabling remote control and automation.
Verdict
Common use cases
- Audit climate devices across office floors
- Generate inventory reports for facility ops
- Check which rooms have Sensibo coverage
- Compare device models before bulk upgrades
- Document pod locations for new hires
Integration
- Vendor
- Sensibo
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
sensibo
Tools
- Get All Sensibo Devices
Tool to retrieve all sensibo pods for the authenticated user. use when you need an up-to-date list of all devices linked to your sensibo account.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Sensibo in the MCP directory and click Connect. 3. You'll be prompted to enter a Sensibo API key. 4. Log into your Sensibo account at home.sensibo.com, go to Settings, then API, and generate a new key. 5. Copy the key and paste it into the Switchy dialog, then click Authorize. 6. Switchy confirms the connection by fetching your device count. 7. Open any Space and type '@Sensibo show me all my devices' to test — you should see a list of your pods with their locations and models. 8. If the list is empty, verify the API key has read permissions and that your Sensibo account actually has registered devices.
What teammates see: by default, memories from Sensibo are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Device Inventory Report
@Sensibo get all my devices and create a table showing the room name, device model, and any notes about each pod.Open in a Space →
Coverage Gap Analysis
@Sensibo show me all devices, then tell me which rooms or floors are missing coverage based on the list.Open in a Space →
Model Comparison Prep
@Sensibo fetch all my pods and group them by model number so I can see which hardware is oldest.Open in a Space →
Onboarding Checklist
@Sensibo list all devices with their room assignments and export it as a simple checklist for onboarding.Open in a Space →
Maintenance Schedule Seed
@Sensibo get all my devices and suggest a quarterly maintenance schedule based on how many pods I have.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Sensibo show me all my connected AC units and their current status
Found 3 Sensibo pods in your account: 'Living Room' (Sky model, currently off, last temp set to 72°F), 'Bedroom' (Air model, running in cool mode at 68°F, fan on medium), and 'Office' (Sky model, off, last used 2 days ago). All devices report normal connectivity and firmware is up to date.
This example uses the Get All Sensibo Devices tool to fetch a snapshot of your smart AC controllers. Requires a valid API key with read access. Note that this MCP currently provides read-only device listing — control actions (turning units on/off, changing temperature) are not yet exposed through the available tools.
@Sensibo which rooms have AC units that are currently running, and what are their target temperatures?
Currently 1 of your 3 Sensibo pods is active: the Bedroom unit is running in cooling mode with a target of 68°F and medium fan speed. The Living Room and Office units are both powered off. The Bedroom unit has been running for approximately 47 minutes since it was last turned on.
Demonstrates filtering device state to surface actionable information. The MCP retrieves all devices, then the AI reasons over the status fields to answer your question. Useful for quick climate checks across multiple rooms, though you'll need to use the Sensibo app or a future MCP update to adjust settings remotely.
@Sensibo compare energy usage patterns — which of my AC units ran the most in the last week?
Based on the device list, I can see your 3 Sensibo pods and their last-known states, but the current MCP tool doesn't expose historical runtime or energy metrics. To answer this question accurately, you'd need to check the Sensibo app's usage dashboard or wait for an MCP update that includes time-series data retrieval. I can confirm which units are currently active (Bedroom) versus idle (Living Room, Office).
This example intentionally shows a limitation: the MCP's single tool retrieves device snapshots, not historical analytics. The AI transparently explains the gap rather than inventing data. Useful for setting expectations — if your workflow depends on usage trends or scheduling history, you'll need to supplement this MCP with app-based checks or request vendor API expansion.
Use-case deep-dives
When a single-device MCP makes sense for distributed teams
A 6-person remote team shares a coworking space in Austin three days a week. The office manager uses Switchy to run a morning standup agent that checks the Sensibo pod status before anyone arrives—confirming the AC ran overnight and the space is cool by 9am. This MCP works because it's one tool, one auth scope, and the query happens once per day. The agent logs the temperature to a shared doc so the team knows whether to bring a sweater. If you're managing more than three locations or need historical trends, you'll want a broader facilities MCP or a direct Sensibo API integration. For a single shared space with a predictable check-in cadence, this MCP keeps the workflow inside Switchy without adding complexity.
Using Sensibo data in a personal productivity agent
A solo consultant in Phoenix runs a weekly energy review agent in Switchy that pulls Sensibo device status alongside calendar density and focus-time logs. The agent flags weeks when the AC ran during empty calendar blocks, surfacing $40-60 in wasted cooling costs per month. This scenario works because the MCP's single tool is enough—there's no need for device control, just a snapshot of what's running. The consultant schedules the agent to run Sunday nights and drops the output into a personal finance tracker. If you want to automate thermostat adjustments or compare multiple smart-home platforms, this MCP won't cover it. For a lightweight audit that ties climate data to work patterns, it's a clean fit.
When Sensibo monitoring hits its ceiling at 3+ locations
A 4-location coffee chain in Seattle uses Switchy to coordinate opening checklists across managers. The ops lead tried adding a Sensibo check to confirm each store's HVAC was online before the 6am shift, but the single-tool MCP requires separate queries per device—no batch status, no alerting logic. By the third location, the workflow was too manual. The team switched to a facilities-focused MCP that aggregates device health across brands. This MCP works if you have one or two Sensibo pods and the check is a nice-to-have, not a blocker. Once climate monitoring becomes part of your opening SOP or you're managing a mixed IoT stack, the single-tool scope becomes a liability. For a pilot or a single flagship location, it's worth testing.
Frequently asked
What does the Sensibo MCP do in Switchy?
It connects your Sensibo smart AC controllers to Switchy's AI workspace. Your team can query device status, retrieve pod lists, and check climate settings across all linked Sensibo units without opening the Sensibo app. Useful for facilities teams managing multiple locations or automating HVAC reporting.
Do I need a Sensibo API key to set this up?
Yes. You generate an API key from your Sensibo account dashboard, then paste it into Switchy during setup. The key grants read access to your devices. If you manage multiple properties under one Sensibo account, the same key works for all pods.
Can the Sensibo MCP change temperature or turn devices on and off?
No. This integration currently retrieves device lists and status only. You cannot send control commands like adjusting temperature or switching modes through Switchy. For write operations, use the Sensibo mobile app or their full REST API directly.
Why use this instead of the Sensibo app or API?
The MCP saves you from writing API scripts when you just need device data in a shared workspace. Your team can ask natural-language questions about pod status without learning Sensibo's API docs. If you need automation or control logic, stick with their API.
Who on the team should connect the Sensibo MCP?
Whoever owns the Sensibo account and can generate API keys. That person typically manages your building's HVAC setup. Once connected, any Switchy workspace member can query the devices, but only the connector can revoke or rotate the API key.