Introduction
The Airthings MCP (Model Context Protocol) connector lets AI assistants interact directly with your Airthings workspace to read sensor data, device status, and indoor air quality metrics through natural language. Instead of building custom API integrations, developers can expose Airthings data to any MCP-compatible AI client with a single connection.
What It Does
The connector gives an AI assistant read-only access to your Airthings account. Once connected, the assistant can:
- Browse your workspace - list accounts, locations, and devices across your entire fleet
- Read live sensor data - fetch the latest readings for any device (CO₂, radon, temperature, humidity, VOC, PM, pressure, and more)
- Query historical trends - retrieve time-series data at hourly, daily, or weekly resolution for any sensor and date range
- Check device health - inspect battery levels, firmware versions, connectivity status, and signal strength
- Get location-level fleet status - see which devices are online, offline, or need attention across a building in a single call
- Generate IAQ summaries - get aggregated indoor air quality overviews for a location without querying each device individually
Authentication and Access Control
The MCP server authenticates using your Airthings API credentials. Access is scoped to the accounts and locations your user has permission to see. Admin access is required for all read operations. The connector is strictly read-only; it cannot modify device settings, move devices, or write any data back to your account.
Sensor Reference
The following sensors are available across compatible devices. Not all sensors are present on all device models.
| Sensor key | Description | Unit |
|---|---|---|
temp | Air temperature | °C |
co2 | Carbon dioxide concentration | ppm |
humidity | Relative humidity | % |
radon | Radon concentration (short-term avg) | Bq/m³ |
voc | Volatile organic compounds | ppb |
pm1 | Particulate matter < 1 µm | µg/m³ |
pm25 | Particulate matter < 2.5 µm | µg/m³ |
pm10 | Particulate matter < 10 µm | µg/m³ |
pressure | Atmospheric pressure | hPa |
pressure_difference | Differential pressure | Pa |
mold | Mold risk index | 0–10 |
light | Light presence | — |
lux | Illuminance | lx |
sound | Sound level | dB |
Units default to metric. Temperature can be overridden to Fahrenheit and radon to pCi/L using the unit_preferences parameter on airthings-get-sensor-history.
Resolution and Rate Limits
When querying historical data, choose resolution based on the time range to stay within the 500 samples-per-device cap:
| Time range | Recommended resolution |
|---|---|
| Up to 1 day | HOUR or FULL |
| 1-7 days | HOUR or FOUR_HOURS |
| 1-4 weeks | DAY |
| 1-6 months | DAY or THREE_DAYS |
| 6+ months | WEEK |
For building-wide queries (50+ devices), always use DAY or coarser HOUR resolution across a large fleet will exceed the aggregate 5000-sample cap and the request will be refused.
Notes on Access Control
- Admin role is required to list devices, query sensor data, and check fleet status.
- User role grants access to dashboards but is not sufficient for MCP tool calls.
- The connector is read-only meaning no write, delete, or configuration operations are supported.
- Device serial numbers and location IDs are treated as internal identifiers and are not surfaced to end users.
Updated about 10 hours ago