
This server wraps the Open-Meteo Air Quality API, giving you free access to air pollution data without authentication. It's part of the Pipeworx gateway ecosystem, which aggregates 673+ data sources behind a unified MCP interface. You can either connect directly to the air quality endpoint or use the full Pipeworx gateway and query it with natural language through ask_pipeworx. The source doesn't list specific tools, but Open-Meteo typically provides PM2.5, PM10, ozone, and other pollutant measurements by coordinates. Reach for this when you need to check air quality conditions in your app or agent workflow without managing API keys.
Air Quality MCP — wraps air-quality-api.open-meteo.com (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_air_quality | Check current air quality at a location (latitude/longitude or city name, e.g., "40.7128, -74.0060" or "New York"). Returns US AQI score, PM2.5, PM10, CO, NO2, and ozone levels. |
get_forecast | Get hourly air quality forecast for a location. Returns US AQI, PM2.5, and PM10 predictions. Use to plan activities or alert users to upcoming poor air conditions. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"airquality": {
"url": "https://gateway.pipeworx.io/airquality/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/airquality/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Airquality data" })
The gateway picks the right tool and fills the arguments automatically.
MIT