Weather

What Weather MCP server does

Weather provides MCP tools for querying weather data for locations worldwide. It uses Open-Meteo as its data source, which aggregates information from national meteorological agencies such as NOAA and DWD. The service covers three time ranges:

• Current observations through get_weather
• Forecasts from one to 16 days through get_forecast
• Historical daily data back to 1940 through get_historical

Location inputs can be city names, city-and-country combinations, US or UK postal codes, or explicit latitude and longitude values. Coordinates are useful for remote, offshore, or ambiguous locations.

How it works

The hosted MCP endpoint is exposed through the Pipeworx gateway at https://gateway.pipeworx.io/weather/mcp. A client can connect to that URL directly, or use the full Pipeworx gateway at https://gateway.pipeworx.io/mcp. The pack endpoint lists the weather tools along with shared Pipeworx meta-tools, including routing and discovery functions.

Weather data is cached by Pipeworx for short periods. Current conditions have an approximately 10-minute refresh interval, hourly forecasts refresh every one to three hours, and daily forecasts refresh about every six hours. Forecast times are returned in UTC by default, along with the location timezone for client-side conversion.

The same tools can also be called over HTTP. For local MCP setups, the @pipeworx/mcp-weather npm package starts a stdio bridge that forwards requests to the hosted gateway, so it needs network access and does not provide offline operation.

Setup and configuration

Add the hosted endpoint to an MCP client such as Claude Desktop, Cursor, or Windsurf:

{
  "mcpServers": {
    "weather": {
      "url": "https://gateway.pipeworx.io/weather/mcp"
    }
  }
}

For a local stdio connection, run the package with npx:

{
  "mcpServers": {
    "weather": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-weather"]
    }
  }
}

Anonymous npm-bridge usage is capped at 50 calls per day. Setting PIPEWORX_API_KEY with a Pipeworx account raises the limit to 200 calls per day. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the gateway-wide meta-tools. The hosted endpoint does not require an account or API key for initial calls.

Tools and capabilities

get_weather returns live temperature in Fahrenheit, feels-like temperature, humidity, wind speed and direction, sky conditions, and the observation time. It is intended for questions about conditions right now.

get_forecast returns daily high and low temperatures, precipitation probability and amount, conditions, and sunrise and sunset. It defaults to seven days and supports forecasts up to 16 days.

get_historical returns daily high and low temperatures, precipitation, and conditions for a requested date range. Without dates, it uses the previous 30 days. ERA5 reanalysis from ECMWF supplies the historical record.

Limitations and notes

Forecast timestamps are UTC unless the client converts them using the returned timezone. Precipitation probability and precipitation amount describe different measurements and should be handled separately. Forecast confidence decreases at longer ranges, especially beyond the first several days.

Open-Meteo hazard fields are less suitable than the NOAA National Weather Service active-alert API for severe-weather workflows in the United States. The npm bridge forwards requests to the gateway and therefore cannot work without network connectivity.

The hosted gateway caches repeated requests for roughly 10 minutes, while anonymous and authenticated usage limits apply to the local npm bridge.