Air Q
Wire your coding agent to read live air-Q sensor readings over HTTP for dashboards, alerts, or automation scripts.
Overview
air-Q MCP is a MCP server for the Build phase that exposes direct HTTP access to local air-Q air quality sensors for coding agents.
What is this MCP server?
- Stdio MCP transport via PyPI package mcp-airq (v1.6.3)
- Direct HTTP to on-prem air-Q devices without cloud dependency
- Configure devices via AIRQ_CONFIG_FILE path or inline AIRQ_DEVICES JSON
- Suited for local labs, smart-home, and facility monitoring side projects
- Model Context Protocol server—not a standalone agent skill
- Server version 1.6.3 on PyPI identifier mcp-airq
- Stdio transport only in published server schema
- 2 configuration env vars: AIRQ_CONFIG_FILE and AIRQ_DEVICES
What problem does it solve?
Agents cannot read your LAN air-Q sensors unless you hand-roll HTTP calls and device config every time.
Who is it for?
Indie builders with physical air-Q units who want agent-driven monitoring, scripting, or MVP dashboards on local HTTP.
Skip if: Teams that only have cloud-linked devices and no local HTTP access—use air-Q Cloud MCP instead.
What do I get? / Deliverables
Your agent gains MCP tools to pull air quality metrics from configured devices using one stdio server registration.
- Registered stdio MCP server the agent can invoke for air-Q HTTP reads
- Repeatable device configuration via env vars without per-chat HTTP boilerplate
Recommended MCP Servers
Journey fit
How it compares
MCP device integration over stdio, not a curated skills marketplace listing or generic web-scraping skill.
Common Questions / FAQ
Who is Air Q MCP for?
Solo and indie builders running Air Q hardware on a local network who want Claude Code, Cursor, or Codex to query live air quality data through MCP tools.
When should I use Air Q MCP?
Use it during build or operate when your agent must read on-prem Air Q sensors via HTTP and you prefer file- or env-based device configuration without the Cloud API.
How do I add Air Q MCP to my agent?
Install the mcp-airq PyPI package, add a stdio MCP server entry in your agent config, and set AIRQ_CONFIG_FILE or AIRQ_DEVICES with your device definitions.