Airthings Consumer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRTHINGS_CLIENT_ID | Yes | Your Airthings client ID | |
| AIRTHINGS_CLIENT_SECRET | Yes | Your Airthings client secret |
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 |
|---|---|
| airthingsB | Get information about my Airthings air quality monitoring devices and their current sensor readings. |
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 1 tool
Only one tool exists, so there is no risk of ambiguity or confusion between tools.
With a single tool, naming consistency is inherently maintained, even though the name 'airthings' is a noun rather than following a verb_noun pattern.
The server has only one tool, which is too few for managing Airthings devices and sensor data; a typical scope would require multiple tools for different operations.
A single tool covering all device information and sensor readings lacks specificity and modularity; agents cannot perform targeted operations like retrieving data for a specific device or sensor type.