Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Sensibo (BYOK) icon

Sensibo (BYOK)

Read your Sensibo smart air conditioner controllers and room sensors: devices, AC state history, measurements, events, timers and schedules with your own API key

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderSensibounofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Sensibo devices do I have?
Tools called
list_devices
What is the current state of my Sensibo device abcd1234?
Tools called
get_device
What were the last AC settings on my Sensibo device abcd1234?
Tools called
list_ac_states
How did the temperature and humidity change over the last 3 days on Sensibo device abcd1234?
Tools called
get_historical_measurements
What events happened on my Sensibo device abcd1234 in the last 2 days?
Tools called
list_device_events
When was my door sensor ds_abc123 opened or closed today?
Tools called
list_door_sensor_events

About

Sensibo (BYOK) lets an AI assistant read your own Sensibo data through the Sensibo API with a key you supply (Sensibo API key). Read-only: 10 tools (list_devices, get_device, list_ac_states, get_historical_measurements, list_device_events, list_door_sensor_events, get_timer, list_schedules, get_schedule, get_climate_react). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to home.sensibo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Sensibo API (home.sensibo.com) with a BYOK key; documentation: https://support.sensibo.com/api/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List devicesList the Sensibo devices on the account.
  • Get deviceGet one Sensibo device with its current state.
  • List ac statesList the most recent AC states set on a device (latest first), at most 20.
  • Get historical measurementsGet temperature and humidity measurements of a device over the last number of days.
  • List device eventsList events recorded for a device (such as state changes and connections) over the last days.
  • List door sensor eventsList open and close events of a Sensibo door and window sensor over the last days.
  • Get timerGet the timer currently set on a device, if there is one.
  • List schedulesList the AC schedules of a device.
  • Get scheduleGet one schedule of a device by schedule id.
  • Get climate reactGet the Climate React (smart mode) settings of a device.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-sensibo.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 10 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-sensibo.connectorbay.com/mcp
RESTPOST https://byok-sensibo.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-sensibo.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Sensibo API key in the X-Upstream-Key header (get one at home.sensibo.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Sensibo connector: questions and answers

What is the Sensibo connector?

Sensibo (BYOK) lets an AI assistant read your own Sensibo data through the Sensibo API with a key you supply (Sensibo API key). It is a hosted MCP server with 10 tools such as List devices, Get device, List ac states, Get historical measurements, List device events, List door sensor events, published by Unify Dynamics LLC. It is independent and not affiliated with Sensibo.

How do I connect Sensibo to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-sensibo.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-sensibo.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-sensibo.json.

Do I need a Sensibo account or API key?

Yes: this is a bring-your-own-key connector. Create a Sensibo API key at https://home.sensibo.com/me/api and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Sensibo read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Sensibo connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Cloudflare Databases (BYOK)

Read your Cloudflare D1 databases and Hyperdrive connection configurations (no passwords, no queries) with your own API token

Live · MCP + REST5 tools

Cloudflare Device Management (BYOK)

Read your Cloudflare WARP device posture rules and integrations, device settings profiles, managed networks, client versions and deployment groups with your own API token

Live · MCP + REST9 tools

Cloudflare DEX (BYOK)

Read your Cloudflare Digital Experience Monitoring synthetic tests, test analytics overview, live fleet status totals and colo list with your own API token

Live · MCP + REST6 tools

Cloudflare DLP (BYOK)

Read your Cloudflare Zero Trust data loss prevention profiles, entries, datasets, data classes, validators and usage limits with your own API token

Live · MCP + REST10 tools

Cloudflare DNS Services (BYOK)

Read your Cloudflare DNS settings, DNSSEC status, DNS analytics, DNS Firewall clusters, secondary DNS and custom nameservers, with your own API token

Live · MCP + REST11 tools

Cloudflare Email Routing (BYOK)

Read your Cloudflare Email Routing settings, DNS records, routing rules and verified destination addresses with your own API token

Live · MCP + REST8 tools

Documentation

Back to top

Sensibo (BYOK) — connector documentation

  • MCP endpoint: https://byok-sensibo.connectorbay.com/mcp
  • REST API: POST https://byok-sensibo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sensibo.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Sensibo Sensibo API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-sensibo.connectorbay.com/health · Tool schemas: https://byok-sensibo.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-sensibo · agent@connectorbay.com

What Sensibo (BYOK) is for

Sensibo (BYOK) lets an AI assistant read your own Sensibo data through the Sensibo API with a key you supply (Sensibo API key). Read-only: 10 tools (list_devices, get_device, list_ac_states, get_historical_measurements, list_device_events, list_door_sensor_events, get_timer, list_schedules, get_schedule, get_climate_react). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to home.sensibo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Sensibo devices do I have?"
  • "What is the current state of my Sensibo device abcd1234?"
  • "What were the last AC settings on my Sensibo device abcd1234?"
  • "How did the temperature and humidity change over the last 3 days on Sensibo device abcd1234?"
  • "What events happened on my Sensibo device abcd1234 in the last 2 days?"
  • "When was my door sensor ds_abc123 opened or closed today?"

What it does

  • list_devices: List the Sensibo devices on the account. Use the fields parameter to choose which properties come back, or * for all.
  • get_device: Get one Sensibo device with its current state. Use fields to pick properties or * for all.
  • list_ac_states: List the most recent AC states set on a device (latest first), at most 20.
  • get_historical_measurements: Get temperature and humidity measurements of a device over the last number of days.
  • list_device_events: List events recorded for a device (such as state changes and connections) over the last days.
  • list_door_sensor_events: List open and close events of a Sensibo door and window sensor over the last days.
  • get_timer: Get the timer currently set on a device, if there is one.
  • list_schedules: List the AC schedules of a device.
  • get_schedule: Get one schedule of a device by schedule id.
  • get_climate_react: Get the Climate React (smart mode) settings of a device.

BYOK key

You bring your own Sensibo Sensibo API key (https://home.sensibo.com/me/api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to home.sensibo.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Sensibo API (home.sensibo.com) with a BYOK key; documentation: https://support.sensibo.com/api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Sensibo account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Sensibo (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Sensibo (BYOK) is. Sensibo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Sensibo data: Read your Sensibo smart air conditioner controllers and room sensors: devices, AC state history, measurements, events, timers and schedules with your own API key. You bring your own Sensibo Sensibo API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Sensibo call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to home.sensibo.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Sensibo rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Sensibo receives. The request we make on your behalf, including the key and the arguments, under Sensibo's own terms and privacy policy. Sensibo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Sensibo gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Sensibo data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Sensibo (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Sensibo at any time to end all access.

Children. Sensibo (BYOK) is a general-audience service operated by the adult using the assistant, under Sensibo's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Sensibo (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Sensibo (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Sensibo (BYOK) provides: Read your Sensibo smart air conditioner controllers and room sensors: devices, AC state history, measurements, events, timers and schedules with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Sensibo credentials and only access data you are allowed to access. Sensibo's terms apply to your use of Sensibo; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Sensibo returns, lightly trimmed; it may be incomplete, delayed or changed by Sensibo. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Sensibo account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Sensibo's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Sensibo may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Sensibo key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Sensibo takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-sensibo

Sensibo (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Sensibo (BYOK) never asks for them.

Get Sensibo (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Sensibo Sensibo API key. Create one at https://home.sensibo.com/me/api, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Sensibo. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Sensibo.