Ambient Weather for AI agents
Ambient Weather makes personal weather stations and an API for pulling real-time and historical readings from them. Homeowners and weather enthusiasts use it to monitor conditions from their own devices. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Ambient Weather.
List connected weather stations
Retrieve every personal weather station registered to the account, with its device ID.
Check the latest station readings
Read current temperature, humidity, and wind data reported by a specific weather station.
Verify a station is reporting
Confirm a device is online and sending fresh data before relying on its readings for a decision.
1 Ambient Weather actions, graded by risk.
Every Ambient Weather action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- ambient_weather.get_devicesGet Devices
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Ambient Weather in three steps.
- 01Your users connect Ambient WeatherThey add their Ambient Weather api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Ambient Weather through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ambient_weather', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ambient Weather connects.
Users add their Ambient Weather api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Ambient Weather connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Ambient Weather from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Ambient Weather and Arc0, answered.
Can I use Ambient Weather with Claude, ChatGPT or Cursor?
Yes. Connect Ambient Weather to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Ambient Weather actions you allow.
How do users connect Ambient Weather?
Users add their Ambient Weather api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Ambient Weather actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Ambient Weather?
Yes. Allow read actions and deny writes in the Ambient Weather policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Ambient Weather too?
Yes. The same Ambient Weather connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ambient Weather into your agent.
Your users connect Ambient Weather once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan