OpenWeatherMap for AI agents
OpenWeatherMap provides current weather, forecasts, and geocoding data, used by developers and planning tools that need weather conditions for a location. 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 OpenWeatherMap.
Get current weather for a location
Pull current conditions, like temperature and precipitation, for a place.
Geocode a location to coordinates
Convert a place name into latitude and longitude for further weather lookups.
Check a forecast before scheduling an event
Read the forecast for a date and location before recommending whether to plan an outdoor event.
2 OpenWeatherMap actions, graded by risk.
Every OpenWeatherMap action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
2Create and change things. Allow, or ask the user first.
- openweathermap.weatherWeather Info
- openweathermap.geocode_locationGeocode Location to Coordinates
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
OpenWeatherMap in three steps.
- 01Your users connect OpenWeatherMapThey add their OpenWeatherMap no auth on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “weather Info” can wait for the user to approve.
- 03Any agent can actYour agent calls OpenWeatherMap through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('openweathermap', { read: 'allow', write: 'ask', // weather destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How OpenWeatherMap connects.
OpenWeatherMap needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
The same OpenWeatherMap 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
- No auth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use OpenWeatherMap from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
OpenWeatherMap and Arc0, answered.
Can I use OpenWeatherMap with Claude, ChatGPT or Cursor?
Yes. Connect OpenWeatherMap 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 OpenWeatherMap actions you allow.
How do users connect OpenWeatherMap?
OpenWeatherMap needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
Which OpenWeatherMap actions can my agent take?
2 in total: 0 read, 2 write and 0 destructive, such as “weather Info”. Your policies decide which of them each agent may call.
Can I make my agent read-only in OpenWeatherMap?
Yes. Allow read actions and deny writes in the OpenWeatherMap policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call OpenWeatherMap too?
Yes. The same OpenWeatherMap connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug OpenWeatherMap into your agent.
Your users connect OpenWeatherMap once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan