Weather MCP server

Weather — Current Conditions and Forecast

Current weather and 7–10 day forecast for any location. Backed by Open-Meteo (https://open-meteo.com), a free aggregator of national meteorological agency data (NOAA in the US, DWD in Germany, etc.). Returns temperature, humidity, wind, precipitation, conditions. Free, no auth, no API key.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Why this matters for AI agents

Weather is one of those things agents need to know about constantly — for travel planning, agricultural questions, energy demand context, event planning, real estate ("is this market in a flood zone with active flooding?"). Open-Meteo is the right backend: free, accurate, global coverage, no key gymnastics.

Common flows:

• Current conditions. "Weather in Tokyo right now" → get_weather({location: "Tokyo"}) → temp, humidity, wind, conditions.
• Forecast. "7-day forecast for Denver" → get_forecast({location: "Denver"}) → daily highs/lows, precipitation chance.
• By coordinates. get_weather({latitude: 39.74, longitude: -104.99}) for places that don't geocode well by name.

Auth

None. Open-Meteo is free and unauthenticated. Generous fair-use limits (~10,000 requests/day per IP). Pipeworx caches per-location for short windows so repeated calls don't burn your daily quota.

Geocoding

The location parameter accepts:

• City names ("Tokyo", "London", "Denver")
• City + country ("Paris, France" to disambiguate from Paris, TX)
• ZIP/postal codes ("94070" for US, "SW1A 1AA" for UK)
• Coordinates as a separate latitude + longitude argument

For ambiguous names, the tool returns a disambiguation hint. For weird locations or precision-sensitive queries (offshore, remote), pass coordinates directly.

Update cadence

Pipeworx caches with a 10-minute TTL so repeated calls within that window are cheap.

Common pitfalls

• Time zones. Forecast hours are in UTC by default. The tool also returns the location's timezone — convert client-side when displaying to users.
• Precipitation probability vs. amount. "70% chance of rain" and "0.4 inches expected" are different fields. For agricultural and travel use, both matter; report both.
• Forecast accuracy degrades by day. Day 1 is reliable; day 7+ is "directional weather signal." Don't quote 10-day forecasts as confident predictions.
• Severe weather events. Open-Meteo has hazard fields but they're less reliable than NWS active alerts for the US. For severe weather agents, layer NOAA NWS API on top.
• Historical weather. Default tools are present + future. For historical data (yesterday and back), Open-Meteo has separate endpoints — let the team know via pipeworx_feedback if that's needed.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/weather/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.