national-weather-service

3.9

national-weather-service is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.

If you are the rightful owner of national-weather-service and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The National Weather Service MCP Server provides access to comprehensive national weather data, including current forecasts, historical data, and alerts.

zone_id_forecast

Forecast data for zone. Example: /zones/forecast/MOZ028/forecast

Try it

Result:

locations_location_id

A product for a location that has issued a product for a specific type. Example: /products/types/AFD/locations/EAX

Try it

Result:

types_type_id

A list of products by type. Example: /products/types/AFD

Try it

Result:

forecast_hourly

Hourly forecast data for a point. This response is derrived from the /gridpoints endpoint and is intentionally less structured. If more structure is required, developers should use the /gridpoints endpoint directly. Example: /points/39.0693,-94.6716/forecast/hourly

Try it

Result:

wfo_x_y

Raw (commonly referred to as "gridded") data provided by the Weather Office. Every forecast request will use this data to build the forecast response. The grid for a given location is determined by the "property.forecastGridData" property in the /points/{lat},{lon} endpoint. Example: /gridpoints/EAX/40,48

Try it

Result:

zone_zone_id

A list of active alerts by zone id. The ATOM format returns items in CAP-ATOM. Example: /alerts/active/zone/ILZ081

Try it

Result:

products_product_id

Data of a product.Example: /product/NWS-IDP-PROD-2202326-2064512 (this id is likely now an expired product)

Try it

Result:

station_id_observations

A list of observations for a station. NOTE! The API uses MADIS to provide observation data. The observation may be delayed while MADIS completes quality checks of the data. To limit the delay, the API is provided with incremental updates with various levels of checked data, and the API will return the variation of the observation with the most checked data. It is possible that no data is provided on the first variation, or that no data is checked on the first variation. It is up to the consumer to determine if the quality of data is appropriate. If not, the previous observation can be requested, or the next nearest station can be used. The API returns the state of the data for each value in the response, where "Z" (or "null") is for not checked (and may never be for some values) and "V" for checked. Please refer to MADIS for complete documentation on their data quality process. Example: /stations/KMKC/observations

Try it

Result:

products_types

A list of product types with an active product

Try it

Result:

point_stations

Stations nearest to a point in order of distance. Example: /points/39.0693,-94.6716/stations

Try it

Result:

alerts_alert_id

A specific alert by id provided by a search or list. Example: /alerts/NWS-IDP-PROD-2202530-2064731

Try it

Result:

active_count

A list of active counts for regions, areas and zones. A list of these items forthcoming.

Try it

Result:

products_locations

A list of locations with active products.

Try it

Result:

alerts_active

A list of active alerts that can be filtered by parameters. Uses same parameters as the /alerts endpoint, but sets "active" parameter to 1 and ignores "start" and "end" parameters. The ATOM format returns items in CAP-ATOM.

Try it

Result:

type_zone_id

Metadata for a zone. Example /zones/forecast/MOZ028

Try it

Result:

area_area

A list of active alerts by area. The ATOM format returns items in CAP-ATOM.

Try it

Result:

point_forecast

Forecast data for a point. The DWML format is a temporary format to aid transition and will be sunset at a later date. This response is derrived from the /gridpoints endpoint and is intentionally less structured. If more structure is required, developers should use the /gridpoints endpoint directly. Example: /points/39.0693,-94.6716/forecast

Try it

Result:

location_id_types

Metadata about a Weather Office. Example /offices/EAX

Try it

Result:

observations_record_id

Data for a specific observation. NOTE! See note in /stations/{stationId}/observations for important details on observation data. Example: /stations/KMKC/observations/2017-01-04T18:54:00+00:00

Try it

Result:

stations

A list of stations and station metadata that can be filtered by parameters. If no parameters are provided, then all stations are returned. This list is not configured by field offices and only returns active stations. Example: /stations?limit=10&states=KS,MO

Try it

Result:

alerts_parameters

A list of alerts that can be filtered by parameters. If no parameters are provided, then all alerts are returned. The ATOM format returns items in CAP-ATOM.

Try it

Result:

region_region

A list of active alerts by region. The ATOM format returns items in CAP-ATOM. Example: /alerts/active/region/GL

Try it

Result:

points_point

Metadata about a point. This is the primary endpoint for forecast information for a location. It contains linked data for the forecast, the hourly forecast, observation and other information. Example: /points/39.0693,-94.6716

Try it

Result:

type_id_locations

A list of locations that have issues products for a type. Example: /products/types/AFD/locations

Try it

Result:

observations_current

The most current observation for a station. Due to a legacy requirement, this endpoint will support XML for the near future when using the Accept header. It is highly recommend that applications update to the JSON format. NOTE! See note in /stations/{stationId}/observations for important details on observation data. Example: /stations/KMKC/observations/current

Try it

Result:

stations_station_id

Metadata about a station. Similar to /stations endpoint with id parameter. Example: /stations/KMKC

Try it