Skip to main content
Glama
michaelahern

Airthings Consumer MCP Server

by michaelahern

Airthings Consumer MCP Server

npm node downloads Ask DeepWiki

A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.

Claude Desktop

Download airthings-consumer-mcp.mcpb from Releases

Installation

Screenshot

Screenshot of Claude Desktop showing a sample interaction with Airthings Consumer MCP Server

Related MCP server: Device MCP Server

Claude Code

Config: .mcp.json

$ claude
╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code!                         │
│                                                   │
│   /help for help, /status for your current setup  │
│                                                   │
│   cwd: /workspaces/airthings-consumer-mcp         │
╰───────────────────────────────────────────────────╯

> Use #airthings to get the current indoor air quality and provide an opinion on the current readings.

● Kitchen Air Quality - Very Good

  Excellent readings:
  - Radon: 0.89 pCi/L (well below EPA action level)
  - CO2: 465 ppm (good ventilation)
  - Temperature: 69.6°F (comfortable)
  - VOCs: 114 ppb (improved from earlier, good level)

  Good readings:
  - PM2.5/PM1: 2 mg/m³ (low particulate matter)

  Needs attention:
  - Humidity: 34% (still low - add moisture to reach 40-60%)

  Bedroom device appears offline or not reporting data.

Amazon Q

Config: .amazonq/mcp.json

$ q
✓ airthings_consumer_mcp loaded in 0.95 s


    ⢠⣶⣶⣦⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣤⣶⣿⣿⣿⣶⣦⡀⠀
 ⠀⠀⠀⣾⡿⢻⣿⡆⠀⠀⠀⢀⣄⡄⢀⣠⣤⣤⡀⢀⣠⣤⣤⡀⠀⠀⢀⣠⣤⣤⣤⣄⠀⠀⢀⣤⣤⣤⣤⣤⣤⡀⠀⠀⣀⣤⣤⣤⣀⠀⠀⠀⢠⣤⡀⣀⣤⣤⣄⡀⠀⠀⠀⠀⠀⠀⢠⣿⣿⠋⠀⠀⠀⠙⣿⣿⡆
 ⠀⠀⣼⣿⠇⠀⣿⣿⡄⠀⠀⢸⣿⣿⠛⠉⠻⣿⣿⠛⠉⠛⣿⣿⠀⠀⠘⠛⠉⠉⠻⣿⣧⠀⠈⠛⠛⠛⣻⣿⡿⠀⢀⣾⣿⠛⠉⠻⣿⣷⡀⠀⢸⣿⡟⠛⠉⢻⣿⣷⠀⠀⠀⠀⠀⠀⣼⣿⡏⠀⠀⠀⠀⠀⢸⣿⣿
 ⠀⢰⣿⣿⣤⣤⣼⣿⣷⠀⠀⢸⣿⣿⠀⠀⠀⣿⣿⠀⠀⠀⣿⣿⠀⠀⢀⣴⣶⣶⣶⣿⣿⠀⠀⠀⣠⣾⡿⠋⠀⠀⢸⣿⣿⠀⠀⠀⣿⣿⡇⠀⢸⣿⡇⠀⠀⢸⣿⣿⠀⠀⠀⠀⠀⠀⢹⣿⣇⠀⠀⠀⠀⠀⢸⣿⡿
 ⢀⣿⣿⠋⠉⠉⠉⢻⣿⣇⠀⢸⣿⣿⠀⠀⠀⣿⣿⠀⠀⠀⣿⣿⠀⠀⣿⣿⡀⠀⣠⣿⣿⠀⢀⣴⣿⣋⣀⣀⣀⡀⠘⣿⣿⣄⣀⣠⣿⣿⠃⠀⢸⣿⡇⠀⠀⢸⣿⣿⠀⠀⠀⠀⠀⠀⠈⢿⣿⣦⣀⣀⣀⣴⣿⡿⠃
 ⠚⠛⠋⠀⠀⠀⠀⠘⠛⠛⠀⠘⠛⠛⠀⠀⠀⠛⠛⠀⠀⠀⠛⠛⠀⠀⠙⠻⠿⠟⠋⠛⠛⠀⠘⠛⠛⠛⠛⠛⠛⠃⠀⠈⠛⠿⠿⠿⠛⠁⠀⠀⠘⠛⠃⠀⠀⠘⠛⠛⠀⠀⠀⠀⠀⠀⠀⠀⠙⠛⠿⢿⣿⣿⣋⠀⠀
 ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠛⠿⢿⡧

╭─────────────────────────────── Did you know? ────────────────────────────────╮
│                                                                              │
│        You can enable custom tools with MCP servers. Learn more with         │
│                                    /help                                     │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

/help all commands  •  ctrl + j new lines  •  ctrl + s fuzzy search
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🤖 You are chatting with claude-4-sonnet

> Use #airthings to get the current indoor air quality and provide an opinion on the current readings.

> I'll get the current air quality readings from your Airthings devices and provide an analysis.

🛠️  Using tool: airthings from mcp server airthings_consumer_mcp
 ⋮ 
 ● Running airthings with the param:
 ⋮  {
 ⋮    "arguments": {},
 ⋮    "name": "airthings"
 ⋮  }

> ## Kitchen Air Quality - Very Good Overall

Excellent readings:
• **Radon**: 0.89 pCi/L (well below EPA action level of 4 pCi/L)
• **CO2**: 465 ppm (good ventilation - below 600 ppm is ideal)
• **Temperature**: 69.6°F (comfortable range)
• **VOCs**: 114 ppb (good level for indoor air)

Good readings:
• **PM2.5/PM1**: 2 mg/m³ (low particulate matter levels)
• **Pressure**: 79,226 Pa (normal atmospheric pressure)

Needs attention:
• **Humidity**: 34% (low - ideal range is 40-60% for comfort and health)

Recommendations:
• Consider adding a humidifier to bring humidity up to the 40-60% range
• The low humidity could cause dry skin, respiratory irritation, and static electricity
• All other readings indicate excellent air quality with good ventilation

Bedroom Status:
• Device appears offline or not reporting data - you may want to check the device connection or battery status

Overall, your kitchen has excellent air quality with just the humidity needing some attention!

Available Tools

1 tool
airthingsB

Get information about my Airthings air quality monitoring devices and their current sensor readings.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get information,' implying a read operation, but does not mention authentication, rate limits, data freshness, or whether any side effects occur. This is insufficient for an agent to understand the tool's true behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, direct, and contains no redundant information. Every word contributes to conveying the tool's purpose, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (no parameters, no output schema), the description covers the basic purpose. However, it lacks details about the output structure, such as whether it returns a list or single device, or what sensor readings are included. This makes it minimally adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the schema coverage is 100% (by default). The description adds value by specifying what kind of data is returned (air quality device info and sensor readings), which goes beyond the empty schema. A baseline of 4 is appropriate for no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get information' and the resource 'Airthings air quality monitoring devices and their current sensor readings.' It is specific enough to convey the tool's purpose, though 'information' is slightly vague. No sibling tools exist to cause confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives or any prerequisites. There are no siblings, but even without alternatives, the description lacks context such as intended use cases or frequency of calls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.1.0
    • First observedairthings

TDQS

B3.3/5.0
Disambiguation5/5

Only one tool exists, so there is no risk of ambiguity or confusion between tools.

Naming Consistency5/5

With a single tool, naming consistency is inherently maintained, even though the name 'airthings' is a noun rather than following a verb_noun pattern.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/michaelahern/airthings-consumer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server