MCP.Market

air-Q Cloud MCP server

by CorantGmbH·io.github.CorantGmbH/mcp-airq-cloud·v1.4.6
No reviews yet

MCP server for air-Q Cloud API — access air quality data from anywhere

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars63 downloads/wk

Reviews

Write one

Nobody has reviewed air-Q Cloud yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

air-Q Cloud tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • export_air_quality_history

    Export historical air-Q Cloud sensor data as one CSV or Excel file.

  • get_air_quality

    Get the most recent air quality sensor readings from the air-Q Cloud.

  • get_air_quality_history

    Get historical air quality data from the air-Q Cloud within a time range.

  • list_devices

    List all configured air-Q Cloud devices with their names, IDs, locations, and groups.

  • plot_air_quality_history

    Generate a chart of historical air-Q Cloud sensor data.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan17 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 49 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How air-Q Cloud compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
63
more than 50% of 12,191 servers with a package

What its tools let an agent do: 5 read

Install air-Q Cloud in Claude Code, Cursor or VS Code

claude mcp add mcp-airq-cloud -- uvx mcp-airq-cloud
Add to Cursor

What the publisher says

From the air-Q Cloud repository's README, as published. We do not edit it. Read it on GitHub

mcp-airq-cloud

MCP server for the air-Q Cloud API — access air quality data from anywhere.

Unlike mcp-airq (which communicates directly with devices on the local network), this server uses the air-Q Cloud REST API to retrieve sensor data remotely.

The same mcp-airq-cloud executable also works as a direct CLI when you pass a tool name as a subcommand.

<!-- mcp-name: io.github.CorantGmbH/mcp-airq-cloud -->

Tools

All tools are read-only — the Cloud API does not support device configuration or control.

Installation

pip install mcp-airq-cloud

Or install from source:

git clone https://github.com/CorantGmbH/mcp-airq-cloud.git
cd mcp-airq-cloud
uv sync --frozen --extra dev

CLI Usage

Use the same command directly from the shell:

mcp-airq-cloud list-devices
mcp-airq-cloud get-air-quality --device "Living Room"
mcp-airq-cloud get-air-quality-history --device "Living Room" --last-hours 24 --sensors co2 pm2_5
mcp-airq-cloud plot-air-quality-history --sensor co2 --output-format png --output co2.png
mcp-airq-cloud export-air-quality-history --sensor co2 --output-format xlsx --output co2.xlsx

For historical plots and exports:

  • omit device, location, and group to combine all configured devices into one artifact
  • use location or group to combine only the matching devices
  • plotairquality_history returns one file per requested sensor, with one series per matching device
  • exportairquality_history returns one CSV/XLSX file per request, with rows for all matching devices

The CLI subcommands mirror the MCP tool names. Both styles work:

mcp-airq-cloud list-devices
mcp-airq-cloud list_devices

To force MCP server mode from an interactive terminal, run:

mcp-airq-cloud serve

The CLI is pipe-friendly: successful command output goes to stdout, while tool errors go to stderr with exit code 1. Plot commands can also stream directly to stdout.

mcp-airq-cloud get-air-quality --device "Living Room" | jq '.co2'
mcp-airq-cloud get-air-quality-history --device "Living Room" --compact-json | jq '.columns.co2'
mcp-airq-cloud get-air-quality-history --device "Living Room" --yaml | yq '.columns.co2'
mcp-airq-cloud plot-air-quality-history --sensor co2 --device "Living Room" --output - > co2.png
mcp-airq-cloud export-air-quality-history --sensor co2 --device "Living Room" --output - > co2.xlsx

Historical Data

Three tools provide access to historical sensor data via the air-Q Cloud API:

Plotting charts

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

air-Q Cloud: common questions

Is air-Q Cloud MCP server safe?
Mostly: it is graded B (80/100). Read the air-Q Cloud safety report
How do I install air-Q Cloud?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does air-Q Cloud need an API key?
Yes. The registry entry asks for AIRQ_CLOUD_DEVICES, AIRQ_CLOUD_API_KEY.
Is air-Q Cloud maintained?
The last commit was 91 days ago (2026-08-05). The latest release is v1.4.6.
How does air-Q Cloud compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.