qingping-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QINGPING_APP_KEY | Yes | Your Qingping App Key, copied from the Access management page at developer.qingping.co | |
| QINGPING_APP_SECRET | Yes | Your Qingping App Secret, copied from the Access management page at developer.qingping.co |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qingping_currentA | Latest readings of Qingping sensors (CO₂, PM2.5, PM10, tVOC, temperature, humidity, battery…) with a plain-language level (good / high — ventilate…). readingAt / ageMin give the time and age of the reading: the sensor only sends to the cloud once per report interval (often 15 min). staleWarning appears when the reading is late relative to that interval. |
| qingping_historyA | History of a Qingping sensor over a period. Returns, per metric, min / max / average / first / last value, the time of the min and max, and the minutes spent above thresholds (CO₂ > 1000 and > 1500 ppm, PM2.5 > 15 and > 35, humidity > 60 and > 70 %). With max_points > 0, also returns the series (averaged per bucket) to draw a chart. coverage gives the share of the period actually measured: an empty or partial history means "no data", not "nothing to report". |
| qingping_alertsA | Alerts triggered by a Qingping sensor over a period (thresholds set in the Qingping app, e.g. CO₂ > 1000 ppm). |
| qingping_set_intervalsA | Changes the measurement (collect) and cloud upload (report) intervals of a Qingping sensor. A short report interval gives fresher data but drains the battery faster when the device is not plugged in. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools map to clearly distinct operations: latest readings, historical aggregation, alert retrieval, and interval configuration. There is no meaningful overlap between current vs. history or alerts vs. readings.
All tools use a consistent `qingping_` prefix followed by a concise snake_case noun or verb phrase. The pattern is predictable and readable throughout.
Four tools is well-scoped for a focused sensor-monitoring server, with each tool covering a distinct part of the lifecycle. No tool feels redundant or out of place.
The surface covers live readings, history, alerts, and device interval configuration, which are the core monitoring workflows. A device listing or sensor inventory tool would help multi-sensor setups, but the existing set is otherwise complete.