← All integrations

Sensibo MCP server

19 operations0 webhooks

Read and control Sensibo smart AC controllers (pods), their schedules, timers, Climate React and sensor history.

Try Sensibo with your agent

Connect Sensibo, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Sensibo on my account, then run one read-only example and show me the result.

Runs once, when you ask

Sensibo tools and triggers

Tools are what your agent can do in Sensibo through Corsair's MCP server. Triggers are the Sensibo events a routine can start from.

Schedules

  • CreateWrite

    Create a schedule that applies an AC state at a local time, once or on chosen weekdays.

    schedules.create

  • DeleteDestructive

    Delete one schedule of a pod.

    schedules.delete

  • GetRead-only

    Get one schedule of a pod.

    schedules.get

  • ListRead-only

    List the schedules of a pod.

    schedules.list

  • Set EnabledWrite

    Enable or pause one schedule of a pod.

    schedules.setEnabled

Ac States

  • ListRead-only

    List the current and recent AC states of a pod, newest first.

    acStates.list

  • SetWrite

    Set the AC state of a pod (on/off, mode, fan level, target temperature, swing).

    acStates.set

  • Set PropertyWrite

    Change one property of the AC state of a pod, such as on or targetTemperature.

    acStates.setProperty

Climate React

  • ConfigureWrite

    Set the Climate React thresholds and the AC states it applies; replaces the current Climate React settings.

    climateReact.configure

  • GetRead-only

    Get the Climate React (smart mode) settings of a pod.

    climateReact.get

  • Set EnabledWrite

    Turn Climate React on or off for a pod.

    climateReact.setEnabled

Timer

  • DeleteDestructive

    Delete the timer on a pod.

    timer.delete

Connect Sensibo to Claude, ChatGPT or Cursor

  1. 1

    Connect Sensibo in Corsair

    Add your Sensibo API key once in Corsair. Corsair stores the credential encrypted and makes the Sensibo API calls for your agent, so it never goes into a prompt or a config file. Connect Sensibo

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Sensibo. On a ChatGPT personal plan, connect Sensibo here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Sensibo's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/sensibo, add the Sensibo plugin, and connect with an API key. Then call methods like corsair.sensibo.api.acStates.list() from your app. Corsair syncs data per tenant.

Yes. Sensibo requires an API key from your Sensibo account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Sensibo, GitHub, Notion, Stripe, and the rest. Trigger Sensibo from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for read and control Sensibo smart AC controllers (pods), their schedules, timers, Climate React and sensor history. Common builds include sync jobs, admin tooling, and agents that call Sensibo APIs from your backend. Local DB entities let you query synced Sensibo records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Sensibo API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/sensibo in the open repo. When Sensibo ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Sensibo data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Sensibo data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Sensibo on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Sensibo operations. You can change a link's mode at hub.corsair.dev/me.