Ambient Weather MCP integration for AI agents.
Connect AI agents to Ambient Weather through 3 structured actions, including get device history, get latest device data, and list devices. Review authenticat…
- ACTION CONTRACTS
- 3
- 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 Ambient Weather integration exposes
The Ambient Weather Agent App exposes 3 provider-backed actions for location and data work. Its current contract lets an authorized agent get recent historical observation records for an ambient weather device, get the latest observation record for an ambient weather device, and list ambient weather devices linked to the connected account. 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 Ambient Weather account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ambient Weather capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_device_historyREADGet recent historical observation records for an Ambient Weather device.
INPUTS: macAddress / limit / endDate
get_latest_device_dataREADGet the latest observation record for an Ambient Weather device.
INPUTS: macAddress
list_devicesREADList Ambient Weather devices linked to the connected account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_device_history
macAddressOPTIONAL- The Ambient Weather device MAC address.
limitOPTIONAL- The maximum number of historical records to return.
endDateOPTIONAL- The history end cursor as an ISO 8601 timestamp or Unix millisecond timestamp.
get_latest_device_data
macAddressOPTIONAL- The Ambient Weather device MAC address.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Device History
Get recent historical observation records for an Ambient Weather device. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_device_historyVerify with Get Latest Device Data
Get the latest observation record for an Ambient Weather device. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_latest_device_dataSAFETY BOUNDARY
Operate Ambient Weather with explicit limits
- Authorize Ambient Weather with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Ambient Weather data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Ambient Weather rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ambient Weather task completed successfully.
CONNECTION MODEL
API key
Ambient Weather API key sent as the apiKey query parameter. Create it from your Ambient Weather account page: https://ambientweather.net/account.
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
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Ambient Weather.