MCP server for air-Q Cloud API — access air quality data from anywhere
Connect Runs on your machine
claude mcp add mcp-airq-cloud -e AIRQ_CLOUD_CONFIG_FILE=<AIRQ_CLOUD_CONFIG_FILE> -e AIRQ_CLOUD_DEVICES=<AIRQ_CLOUD_DEVICES> -e AIRQ_CLOUD_API_KEY=<AIRQ_CLOUD_API_KEY> -- uvx mcp-airq-cloud==1.4.6
{
"mcpServers": {
"mcp-airq-cloud": {
"command": "uvx",
"args": [
"mcp-airq-cloud==1.4.6"
],
"env": {
"AIRQ_CLOUD_CONFIG_FILE": "<AIRQ_CLOUD_CONFIG_FILE>",
"AIRQ_CLOUD_DEVICES": "<AIRQ_CLOUD_DEVICES>",
"AIRQ_CLOUD_API_KEY": "<AIRQ_CLOUD_API_KEY>"
}
}
}
}
{
"mcpServers": {
"mcp-airq-cloud": {
"command": "uvx",
"args": [
"mcp-airq-cloud==1.4.6"
],
"env": {
"AIRQ_CLOUD_CONFIG_FILE": "<AIRQ_CLOUD_CONFIG_FILE>",
"AIRQ_CLOUD_DEVICES": "<AIRQ_CLOUD_DEVICES>",
"AIRQ_CLOUD_API_KEY": "<AIRQ_CLOUD_API_KEY>"
}
}
}
}
{
"servers": {
"mcp-airq-cloud": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-airq-cloud==1.4.6"
],
"env": {
"AIRQ_CLOUD_CONFIG_FILE": "<AIRQ_CLOUD_CONFIG_FILE>",
"AIRQ_CLOUD_DEVICES": "<AIRQ_CLOUD_DEVICES>",
"AIRQ_CLOUD_API_KEY": "<AIRQ_CLOUD_API_KEY>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
AIRQ_CLOUD_CONFIG_FILEOptional | Path to the air-Q Cloud device configuration JSON file |
AIRQ_CLOUD_DEVICESOptional, secret | Inline JSON array with configured air-Q Cloud devices |
AIRQ_CLOUD_API_KEYOptional, secret | Global fallback API key (used when per-device api_key is omitted) |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 5 Aug 2026 |
| Last updated | 5 Aug 2026 |
| Registry name | io.github.CorantGmbH/mcp-airq-cloud |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
