Airquality logo

Airquality

Query current and forecast air-quality data by coordinates or city through MCP, with no authentication required.

Install Airquality

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "airquality": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-airquality"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 2 tools correctly (Today).

Overview

The airquality MCP server queries Open-Meteo's air-quality API for current readings and hourly forecasts. It accepts latitude/longitude coordinates or city names and returns AQI and pollutant data through MCP tools. Use it for activity planning, air-quality lookups, or alerts about forecast conditions; it runs through Pipeworx or as a local stdio package.

Use cases

  • Check current AQI for a city
  • Retrieve hourly pollution forecasts
  • Plan outdoor activities around forecast conditions
  • Alert users about upcoming poor air quality

Key features

  • Current US AQI and pollutant readings
  • Hourly US AQI, PM2.5, and PM10 forecasts
  • City-name or coordinate-based locations
  • Gateway and local stdio deployment
  • HTTP tool endpoint access

Tools2

What Airquality lets your agent do. Expand a tool for its parameters.

Verified live~219 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

What it can do

From the 2 tools this server returned when we ran it.

Read-only tools · 2
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age203 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-airquality (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads428Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed2Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Airquality works

What airquality does

The airquality MCP server exposes air-quality data from air-quality-api.open-meteo.com through two MCP tools. It is an independent integration and does not require authentication to use the upstream service. Inputs can identify a location with latitude and longitude, such as 40.7128, -74.0060, or with a city name such as New York.

get_air_quality retrieves current conditions. Its response includes the US AQI score and measurements for PM2.5, PM10, carbon monoxide, nitrogen dioxide, and ozone. get_forecast returns hourly predictions for US AQI, PM2.5, and PM10, which makes it suitable for checking expected conditions before planning outdoor activity or notifying users about upcoming poor air quality.

This project belongs to the 🌳 Environment & Nature category and is intended for agents that need location-based air-quality information rather than a general environmental data system.

How it works

The airquality MCP server can be reached through the Pipeworx gateway or run locally as a stdio MCP process. The gateway exposes the pack endpoint at https://gateway.pipeworx.io/airquality/mcp. A full gateway connection is also available at https://gateway.pipeworx.io/mcp.

The pack endpoint lists the air-quality tools together with shared Pipeworx meta-tools. These include routing and discovery functions such as ask_pipeworx, discover_tools, and search_within, along with memory-related tools. The exact list is provided by the connection's initialize response and may be larger than the two air-quality tools. The local package exposes only this pack's tools and does not provide the shared gateway meta-tools.

Without an MCP client, the gateway also provides HTTP tool endpoints. For example, current conditions can be requested with POST /v1/tools/airquality_get_air_quality and a JSON body containing latitude and longitude.

Setup and configuration

For a gateway connection, add the pack URL to an MCP client's server configuration:

config.json
{
  "mcpServers": {
    "airquality": {
      "url": "https://gateway.pipeworx.io/airquality/mcp"
    }
  }
}

The standalone option uses the published npm package and communicates over stdin/stdout:

config.json
{
  "mcpServers": {
    "airquality": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-airquality"]
    }
  }
}

Run npx -y @pipeworx/mcp-airquality directly to verify that the local process starts. The standalone mode does not need a Pipeworx account or a gateway round trip.

Tools and capabilities

  • get_air_quality: Gets current US AQI, PM2.5, PM10, CO, NO2, and ozone values for a city or coordinate pair.
  • get_forecast: Gets hourly US AQI, PM2.5, and PM10 predictions for a location.
  • HTTP access: Calls the gateway tool endpoint directly when an MCP client is unavailable.
  • Gateway routing: Uses ask_pipeworx to ask questions in plain English when connected through Pipeworx.

Limitations and notes

The integration is unofficial and is not affiliated with, endorsed by, or published by the upstream provider. Forecast output is limited to US AQI, PM2.5, and PM10 predictions, while current-condition output includes the additional listed pollutants. Gateway connections include shared meta-tools by design; use the local stdio package when only the airquality tools are needed.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Airquality

airquality is an MCP server that connects AI clients to Open-Meteo's air-quality API and exposes get_air_quality for current readings and get_forecast for hourly predictions. It accepts coordinates or city names, and returns US AQI plus pollutant measurements including PM2.5, PM10, CO, NO2, and ozone.

Install it as a local MCP process with npx using @pipeworx/mcp-airquality. Add a server entry with command npx and args -y and @pipeworx/mcp-airquality, or run the same npx command directly to confirm it starts.

Yes, airquality works with Cursor through the Pipeworx MCP endpoint. Add https://gateway.pipeworx.io/airquality/mcp as the server URL in the client's MCP configuration. The README also names Claude Desktop and Windsurf as supported setup targets.

No, the documented airquality setup requires no authentication for the upstream air-quality service. The standalone package also runs without a Pipeworx account, while the gateway and local modes provide different connection paths to the same pack tools.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAirquality AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/airquality?style=directory)](https://allmcps.com/mcp/airquality)
HTML Embed
<a href="https://allmcps.com/mcp/airquality"><img src="https://allmcps.com/api/badge/airquality?style=directory" alt="Airquality on AllMCPs" /></a>