OpenWeather MCP integration for AI agents.
Connect AI agents to OpenWeather through 21 structured actions, including get 5 day forecast, add weather station, delete weather station, and submit station…
- ACTION CONTRACTS
- 21
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the OpenWeather integration exposes
The OpenWeather Agent App exposes 21 provider-backed actions for location and data work. Its current contract lets an authorized agent retrieve the openweather 5-day forecast in 3-hour steps for exactly one location selector, create one openweather weather station under the current account, and delete one openweather weather station by identifier. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected OpenWeather account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real OpenWeather capabilities.
Showing 12 of 21 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_5_day_forecastREADRetrieve the OpenWeather 5-day forecast in 3-hour steps for exactly one location selector.
INPUTS: q / id / zip / lat / lon
add_weather_stationWRITECreate one OpenWeather weather station under the current account.
INPUTS: external_id / name / latitude / longitude / altitude
delete_weather_stationHIGH IMPACTDelete one OpenWeather weather station by identifier.
INPUTS: station_id
submit_station_measurementsREVIEWSubmit one or more measurements for existing OpenWeather weather stations.
INPUTS: measurements
get_air_pollution_currentREADRetrieve the current air-pollution snapshot for one latitude and longitude.
INPUTS: lat / lon
get_air_pollution_forecastREADRetrieve the air-pollution forecast for one latitude and longitude.
INPUTS: lat / lon
get_air_pollution_historyREADRetrieve historical air-pollution data for one latitude and longitude over a time range.
INPUTS: lat / lon / start / end
get_circle_city_weatherREADRetrieve current weather for nearby cities around one latitude and longitude by using OpenWeather's compatibility city-search endpoint.
INPUTS: lat / lon / cnt / mode / units
get_current_weatherREADRetrieve the current weather for exactly one OpenWeather location selector.
INPUTS: q / id / zip / lat / lon
get_geocoding_by_zipREADResolve one ZIP or postal code into a named OpenWeather location.
INPUTS: zip
get_geocoding_directREADResolve one place name into one or more OpenWeather geocoding matches.
INPUTS: q / limit
get_geocoding_reverseREADResolve one latitude and longitude pair into one or more named places.
INPUTS: lat / lon / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_5_day_forecast
qOPTIONAL- The city name, optionally followed by state code and country code, such as London,GB.
idOPTIONAL- The OpenWeather city identifier.
zipOPTIONAL- The ZIP or postal code followed by country code, such as 94040,US.
latOPTIONAL- The latitude in decimal degrees.
lonOPTIONAL- The longitude in decimal degrees.
add_weather_station
external_idREQUIRED- The caller-defined external weather-station identifier.
nameREQUIRED- The weather-station display name.
latitudeREQUIRED- The station latitude in decimal degrees.
longitudeREQUIRED- The station longitude in decimal degrees.
altitudeREQUIRED- The station altitude in metres.
delete_weather_station
station_idREQUIRED- The weather-station identifier.
submit_station_measurements
measurementsREQUIRED- The list of weather-station measurements to submit.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get 5 Day Forecast
Retrieve the OpenWeather 5-day forecast in 3-hour steps for exactly one location selector. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_5_day_forecastControl Add Weather Station
Create one OpenWeather weather station under the current account. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_weather_stationVerify with Get Air Pollution Current
Retrieve the current air-pollution snapshot for one latitude and longitude. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_air_pollution_currentSAFETY BOUNDARY
Operate OpenWeather with explicit limits
- Authorize OpenWeather with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_weather_station` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in OpenWeather rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the OpenWeather task completed successfully.
CONNECTION MODEL
API key
OpenWeather API key sent as the appid query parameter. Find or create it on the API keys page in your OpenWeather account: https://openweathermap.org/faq.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 17
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by OpenWeather.