@cyanheads/nws-weather-mcp-server

Public Hosted Server: https://nws.caseyjhand.com/mcp

Overview

US weather data from the National Weather Service API (api.weather.gov). Get forecasts, active alerts, current observations, forecast-office narrative products, and zone-level text forecasts for any coordinate in the 50 states and US territories, plus national alert counts and a station's last ~7 days of observations. Adjacent marine areas are covered by alerts, plus stations and observations near the coast; NWS publishes no point or zone text forecast for them. Runs as a stdio process, a local Streamable HTTP server, or the public hosted endpoint above.

Tools

Resources

Also reachable via the nws_list_alert_types tool, for MCP clients that don't support resources.

Related MCP server: weather-mcp

Capability reference

nws_get_forecast tool

• latitude + longitude; returns named 12-hour periods by default (14, ~7 days), or with hourly: true one-hour periods with dewpoint and humidity, 48 per page of the ~156 upstream

• Returns the forecastZone and county zone codes for chaining into nws_search_alerts; marine coordinates fail with a typed marine_forecast_unsupported error pointing to a nearby land point or nws_search_alerts, and land points NWS serves no forecast grid for with no_forecast_grid

nws_search_alerts tool

• At most one location filter — area, point, zone, region_type, or region — or none for a national search; event matches case-insensitively and partially; status defaults to Actual (also Exercise, System, Test, Draft); limit 1-25 (default 25) per page

• Each affectedZones entry carries its zone type (forecast/county/fire), marking which codes chain into nws_get_zone_forecast; CAP message-lifecycle fields (sent, effective, status, messageType, references) are distinct from the hazard's own onset/ends

nws_get_alert_counts tool

• No input; returns national totalAlerts (landAlerts + marineAlerts), plus areas counts keyed by state/territory or marine area code and regions counts keyed by marine region (AL, AT, GL, GM, PA, PI), each listing only codes with an active alert

• Counts cover every message status, Test and Exercise included, so totalAlerts can exceed a national nws_search_alerts totalCount (status: Actual by default); an alert counts once in each area its zones fall in, so areas can sum past totalAlerts

nws_get_observations tool

• Look up by coordinates (resolves nearest station) or station_id directly

• Dual-unit display on every measurement (F/C, mph/km/h, inHg/hPa, mi/km); observations older than 2 hours carry a staleness notice, and a separate warning flags a station with most measurements unavailable

nws_get_observation_history tool

• station_id (from nws_find_stations); optional start (inclusive) and end (exclusive) as ISO 8601 date-times with seconds and an offset; limit 1-100 (default 24) per page, newest first, back through the ~7 days NWS keeps

• Each observation carries the nws_get_observations measurement fields, null where the station reported nothing; an unknown station fails with station_not_found, and a malformed window or a start not before end with invalid_time_window

• nextCursor appears only when a page fills limit, and pages neither repeat nor skip an observation; no totalCount, since NWS reports none for a window

nws_find_stations tool

• latitude + longitude; optional limit (1-50, default 10) sizes the page

• Nearest first; each result carries the station ID for nws_get_observations, distance (km), bearing, zone codes, elevation, and time zone

nws_list_alert_types tool

• Returns the full set of event types the NWS API recognizes (e.g., "Tornado Warning", "Heat Advisory")

• Use to discover valid values for the event filter in nws_search_alerts

nws_get_office_discussion tool

• office: 3-letter WFO code (e.g., "SEW" for Seattle), returned as the office field by nws_get_forecast; product_type: AFD (default), HWO, ZFP, or SPS

• Returns productText plus issuanceTime, issuingOffice, productName, productCode, wmoCollectiveId; an unknown office, or a valid office with no current product of the requested type, fails with a typed no_products error

nws_get_zone_forecast tool

• zone_id: forecast zone code (e.g., "WAZ315") — returned by nws_get_forecast (forecastZone), nws_find_stations (forecastZone column), and nws_search_alerts (the code of an affectedZones entry with type: "forecast")

• Returns named periods (e.g., "Today", "Tonight", "Monday") with narrative text from local forecasters; county (XXC###), fire, and unknown zone codes fail with a typed zone_not_found error, marine forecast zones (e.g., PZZ251) with marine_forecast_unsupported, and a valid zone NWS publishes no text forecast for with zone_forecast_unavailable, which carries a point inside the zone for nws_get_forecast

nws://alert-types resource

• Static list of all valid NWS alert event type names, returned as application/json

• No parameters; cached publicly for 1 hour

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

NWS-specific:

• Sends the required User-Agent header automatically (configurable via NWS_USER_AGENT) — NWS returns 403 without one

• Automatic coordinate-to-grid resolution via /points, cached for 1h since grid cells rarely change

• Request timeouts plus retry/backoff for transient NWS API failures

• Zero-auth access — no API keys required

• Paged results — nws_get_forecast, nws_find_stations, and nws_search_alerts report totalCount against this page's shown, and nws_get_observation_history reports shown alone (NWS gives no total for a time window); pass the returned nextCursor back as cursor for the next page (omitted on the last page)

Agent-friendly output:

• Provenance — forecast, observation, and station responses echo office codes, time zones, and forecast/county zone codes so agents can chain directly into nws_get_office_discussion, nws_get_zone_forecast, and nws_search_alerts without re-deriving them

• Guidance over silence — empty, truncated, or cursor-past-end results carry a notice naming the cause and the concrete next step, rather than an empty array or a bare page

• Discriminated output contracts — zone type (forecast/county/fire), CAP status/messageType distinct from hazard onset/ends, and typed error reasons (invalid_area_code, no_products, zone_not_found, …) — callers branch on data, not string parsing

• Response shaping — upstream single-unit floats are normalized into dual-unit pairs (F/C, mph/km/h, inHg/hPa, mi/km) and rounded to match what format() renders, so structured and text output agree

Getting started

Public Hosted Instance

A public instance is available at https://nws.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:

{
  "mcpServers": {
    "nws-weather-mcp-server": {
      "type": "streamable-http",
      "url": "https://nws.caseyjhand.com/mcp"
    }
  }
}

Self-Hosted / Local

Add the following to your MCP client configuration file.

{
  "mcpServers": {
    "nws-weather-mcp-server": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@cyanheads/nws-weather-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with npx (no Bun required):

{
  "mcpServers": {
    "nws-weather-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cyanheads/nws-weather-mcp-server@latest"],
      "env": {
        "MCP_TRANSPORT_TYPE": "stdio",
        "MCP_LOG_LEVEL": "info"
      }
    }
  }
}

Or with Docker:

{
  "mcpServers": {
    "nws-weather-mcp-server": {
      "type": "stdio",
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/nws-weather-mcp-server:latest"]
    }
  }
}

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_SESSION_MODE=stateless MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp

Prerequisites

• Node.js v24+ or Bun v1.4+

Installation

1. Clone the repository:

git clone https://github.com/cyanheads/nws-weather-mcp-server.git

2. Navigate into the directory:

cd nws-weather-mcp-server

3. Install dependencies:

bun install

Configuration

See .env.example for the full list including auth, storage, and OpenTelemetry options.

Running the server

Local development

• Build and run the production version:

  # One-time build
  bun run rebuild
  
  # Run the built server
  bun run start:http
  # or
  bun run start:stdio

• Run checks and tests:

  bun run devcheck     # Lints, formats, type-checks
  bun run test         # Runs test suite

Project structure

Development guide

See CLAUDE.md for development guidelines and architectural rules. The short version:

• Handlers throw, framework catches — no try/catch in tool logic

• Use ctx.log for domain-specific logging, ctx.state for storage

• Add new tools/resources to the barrel exports and the createApp() arrays in src/index.ts

• Wrap NWS API calls: validate raw JSON → normalize to domain types → return the output schema; never fabricate missing fields

Contributing

Issues are welcome. Run checks before submitting:

bun run devcheck
bun run test

License

Apache-2.0 — see LICENSE for details.