Weather MCP Server

US weather, alerts, earthquakes and elevation for AI agents, from NWS/NOAA and USGS. No API keys. The weather mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

US weather, hazards and geospatial data for AI agents — as MCP tools your agent can call mid-task for forecasts, alerts, earthquakes and elevation. All from keyless US-government feeds. No API keys.

Its toolset

Everything the assistant can do here goes through one of these:

• geocode — Convert a US street address to latitude/longitude
• weather_forecast — Multi-day or hourly forecast for a US point
• weather_current — Latest observed conditions from the nearest station
• weather_alerts — Active warnings, watches and advisories by US state
• earthquakes — Recent earthquakes, filterable by magnitude, time and area
• elevation — Ground elevation at a latitude/longitude

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Weather's toolset — geocode, weather_forecast, weather_current and 3 more — is a fair guide to whether it matches your workflow. It is maintained by com.datakoot; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the weather mcp server does with a few real requests.