OpenWeatherMap integration
Weather data API providing current weather, forecasts, and historical data worldwide
Say what should happen.
The workflow builds itself.
Common OpenWeatherMap use cases
- get air pollution programmatically
- get forecast 5day programmatically
- get current weather programmatically
- execute geocoding zip programmatically
- execute geocoding direct programmatically
- execute geocoding reverse programmatically
- get air pollution history programmatically
- execute onecall historical programmatically
- get air pollution forecast programmatically
- execute onecall current forecast programmatically
What you can do with OpenWeatherMap
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Air pollution, 1 operation
get_air_pollutionGet air pollutionGETGet current air pollution data
Air pollution forecast, 1 operation
get_air_pollution_forecastGet air pollution forecastGETGet air pollution forecast data for a location.
Air pollution history, 1 operation
get_air_pollution_historyGet air pollution historyGETGet historical air pollution data for a location over a time period.
Current weather, 1 operation
get_current_weatherGet current weatherGETGet current weather data for a location
Forecast 5day, 1 operation
get_forecast_5dayGet forecast 5dayGETGet 5 day / 3 hour weather forecast
Geocoding direct, 1 operation
geocoding_directGeocoding directGETConvert city name to coordinates
Geocoding reverse, 1 operation
geocoding_reverseGeocoding reverseGETConvert coordinates to location name
Geocoding zip, 1 operation
geocoding_zipGeocoding zipGETConvert zip code to coordinates
Onecall current forecast, 1 operation
onecall_current_forecastOnecall current forecastGETGet all weather data in one call (current, minutely, hourly, daily)
Onecall historical, 1 operation
onecall_historicalOnecall historicalGETGet historical weather data for a specific timestamp (data available from 1 January 1979 up to 4 days ahead).
Use OpenWeatherMap from Claude Code, Cursor or Codex
Connect OpenWeatherMap in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its OpenWeatherMap operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect OpenWeatherMap
- Create your workspace
Sign up free. Nothing to install.
- Connect OpenWeatherMap once
Add your OpenWeatherMap connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
OpenWeatherMap integration FAQ
What can you do with the OpenWeatherMap integration?
LiveContext exposes 10 operations on OpenWeatherMap, covering air pollution, air pollution forecast, air pollution history and current weather. Common uses include get air pollution programmatically, get forecast 5day programmatically and get current weather programmatically.
