LOCAL FORECAST INTERFACES

Give an agent a current Smoke Window forecast.

Download one inspectable Node module, then use its JavaScript API, JSON command, local stdio MCP tool, or client-side browser runner. Official NOAA/ECCC, AirNow/AQHI, WFIGS/CWFIS, and Open-Meteo data is downloaded directly to the requesting device.

Download local tool Open browser runner

Version 1.1.1 · Node 22.13.0+ · U.S. HRRR forecasts download approximately 13–18 MiB uncached; Canadian point forecasts use much smaller ECCC responses · no hosted API, remote MCP server, account, key, or forecast history.

INSTALL & VERIFY

Use a versioned local tool

Save and inspect the file, compare its SHA-256 digest with checksums.json, then run it locally. Never pipe a remote script directly into Node. Its single read-only stdio MCP tool is get_smoke_forecast.

JSON CLI

node smoke-window-agent-v1.1.1.mjs forecast --location "Julian, California" --json

OpenAI Codex

codex mcp add smoke-window -- node <absolute-path>/smoke-window-agent-v1.1.1.mjs mcp

Claude Code

claude mcp add smoke-window -- node <absolute-path>/smoke-window-agent-v1.1.1.mjs mcp

MACHINE-READABLE REFERENCES

One contract across every local interface

INTERPRETATION

Model guidance, observed air ratings, and reported fires remain distinct

Smoke Window requires all 17 NOAA or ECCC samples before reporting a clear-window result. The Canadian ECCC field includes wildfire contributions but can also include anthropogenic and biogenic PM2.5. AirNow AQI and ECCC AQHI are observed context. WFIGS and CWFIS incidents are reports whose proximity does not prove smoke origin. Results are planning guidance, not health or life-safety instructions.