air-quality-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport for MCP server, e.g. 'http' for HTTP transport, default likely 'stdio'. | stdio |
| AIRQUALITY_LOCAL_DEV | No | Set to '1' to run in local development mode (serves HTTP). | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_air_qualityA | Get the current air quality for a city, from real-time monitoring and atmospheric model data. Use for any "what's the air quality in X", "is it safe to go outside in Y", "how polluted is Z" style question, or whenever pollen/smog/wildfire-smoke/pollution conditions are relevant to a plan (running, cycling, sensitive-groups advice, travel).
Returns a dict with:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sponsored_card | |
| result_widget_get_air_quality |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is unambiguous and clearly distinct.
The tool name 'get_air_quality' follows the clean verb_noun convention, consistent with typical MCP naming patterns. There are no other names to conflict.
With only one tool, the server feels thin for the broader 'air quality' domain. While it may serve a single lookup use case, the count is borderline.
The tool thoroughly covers current air quality with detailed pollutant data and AQI categories. Minor gaps exist such as historical queries or forecasts, but the core current-condition use case is fully addressed.