The same fleet, reachable four ways: through your AI assistant over the Sensio MCP, through the mobile app, through sensio.co, and through Hyper for deep analysis. Set the question up once, and it keeps answering on its own.
The Sensio MCP server gives your AI assistant read-only access to your own fleet — the same four tools every time, with the call trail visible. No dashboard, no query language, no export. You ask; it reads the sensors and answers.
It runs locally next to your assistant, so your API key never leaves your machine. Point it at one device or your whole estate.
tools, read-only
biological classes
refresh cycle
dashboards to open
Held above limit for three consecutive runs. 30-day trace and subclass breakdown attached.
The MCP is the fastest way to ask a question. These are the surfaces you reach for when you want to glance, to govern, or to go deep.
Your fleet in your pocket. The surface that reaches you rather than the one you go to.
The full platform, in any browser. Where the fleet is managed and the evidence is kept.
The analysis surface. When a reading needs to become a finding you can defend.
Every surface runs on the devices already in your pocket and your bag. Pick the one that matches the moment — they all read the same sensors.
| Surface | iPhone / Android | Mac / PC | iPad / tablet | Any browser |
|---|---|---|---|---|
| Sensio MCPvia your AI assistant | Claude mobile | Desktop & CLI | Claude on iPad | Custom GPT |
| Sensio appnative | — | — | ||
| sensio.coresponsive web | ||||
| Hyperanalysis workspace | Best on large screen |
Monitoring you have to remember to check isn’t monitoring. Every surface can be put on a schedule, so the question gets asked whether or not anyone is at a keyboard.
Save the prompt as a scheduled task in your assistant. It runs the same four tools each morning and only writes back when a threshold has moved.
Set a threshold per parameter, per room. The phone stays quiet until a reading crosses it, then tells you which zone and by how much.
Scheduled PDF summaries to the people who need them, plus alert policies that route to email, Slack or your BMS over BACnet/IP.
Keep a recurring export running into your own analysis stack, with annotations carried through so context survives the handover.
The MCP is the only surface that needs setting up — the app and the web platform just need your login.
On sensio.co, open Settings → API Access and generate a key. Note the serial of any device you want the assistant to see.
Drop the block below into your assistant’s MCP config. Same format for Claude Desktop, Windsurf, Cline and Continue.
Restart the assistant and try “what’s my indoor air quality right now?” — then turn the useful ones into scheduled runs.
Exposes four read-only tools: sensio_list_device_serials, sensio_get_latest, sensio_get_history and sensio_get_particle_breakdown. ChatGPT doesn’t speak MCP — use a Custom GPT with Actions against the same API.
Fifteen minutes, no deck. Tell us how your team already works and we’ll tell you which of the four surfaces to start with — and whether the MCP is worth wiring up on day one or later.
One device is enough to learn something. Connect it to whichever surface fits how you already work — you can add the others later without changing anything.