Sensibo for AI agents
Sensibo makes smart controllers that connect air conditioners and heat pumps to the internet for remote control and scheduling. Homeowners and property managers use it to manage climate remotely. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Sensibo.
List connected AC devices
Pull every Sensibo device on the account to see which units are online across a property.
Check current unit status
Read a device's current temperature, mode, and power state before deciding whether to change it.
Confirm device state before automating
Verify a unit is actually on or off through a read-only check before any automation acts on it.
1 Sensibo actions, graded by risk.
Every Sensibo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- sensibo.get_all_devicesGet All Sensibo Devices
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Sensibo in three steps.
- 01Your users connect SensiboThey add their Sensibo api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Sensibo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('sensibo', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Sensibo connects.
Users add their Sensibo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Sensibo connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Sensibo from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Sensibo and Arc0, answered.
Can I use Sensibo with Claude, ChatGPT or Cursor?
Yes. Connect Sensibo to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Sensibo actions you allow.
How do users connect Sensibo?
Users add their Sensibo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Sensibo actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Sensibo?
Yes. Allow read actions and deny writes in the Sensibo policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Sensibo too?
Yes. The same Sensibo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Sensibo into your agent.
Your users connect Sensibo once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan