Use a name, ID, or point
Start with Seattle, WA. Search for the exact city name. If several places match, you get a list of choices to show the user.
Send a US city name and get National Weather Service observations, forecasts and alerts. Use the REST API or four read-only MCP tools. No API key needed.
curl 'https://bridge.wx.mrkd.co/v1/weather?city=Seattle%2C%20WA'
Observations, forecasts and alerts,
each with its source time.
Start with Seattle, WA. Search for the exact city name. If several places match, you get a list of choices to show the user.
Current weather is a station observation. Forecasts are predictions. Each response says how fresh the data is, what is missing, and whether the alert check failed.
Response semantics →Agents can search cities and get weather, hourly forecasts and NWS alerts, with typed arguments and structured results.
Tools and setup →Success returns {"data": …, "meta": …} with attribution. Errors return {"errors": […]}. Pass exactly one location: city, cityId, or both lat and lon. Add units=us or units=metric.
current is a station observation or null. Check observedAt, ageSeconds, and stale; observations older than two hours are stale.forecast has up to 14 periods; hourly has up to 24. NWS forecast text keeps its original units.alertsStatus: "unavailable" means alerts could not be checked. An empty list does not mean there are no alerts.assembledAt is when the report was built, not when the data were observed. Upstream data are cached for up to 120 seconds.The REST reference calls the live API from this site. To try the MCP tools, open the MCP tool explorer.