How to connect OpenWeather API to OpenClaw
Connect OpenWeather API to OpenClaw with ClawLink: paste your OpenWeather API key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine.
OpenWeather APIAPI KEYMCPProvides access to current weather data, forecasts, and historical weather data for any location worldwide.. Once connected, OpenClaw can read and act on OpenWeather API from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to OpenWeather API access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical OpenWeather API setup: install one ClawHub skill, connect OpenWeather API in the browser, and OpenClaw can call real OpenWeather API actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to OpenWeather API.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect OpenWeather API
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with OpenWeather API?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect OpenWeather API in the ClawLink dashboard — paste your OpenWeather API API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from OpenWeather API, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once OpenWeather API is connected in the dashboard, that agent calls the same 21 OpenWeather API tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
OpenWeather API MCP for OpenClaw
Looking for a OpenWeather API MCP server for OpenClaw? ClawLink connects OpenWeather API to OpenClaw and exposes 21 OpenWeather API tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes OpenWeather API integration works the same way.
What the OpenClaw OpenWeather API integration can do
21 OpenWeather API tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 21.
20 of 21 OpenWeather API tools for OpenClaw
| Tool | What it does |
|---|---|
Get air pollution current openweather_api_get_air_pollution_current | Fetch current air pollution data for a location |
Get air pollution forecast openweather_api_get_air_pollution_forecast | Get forecasted air pollution data for a specific location |
Get air pollution history openweather_api_get_air_pollution_history | Retrieve historical air pollution data |
Get circle city weather openweather_api_get_circle_city_weather | Search for current weather data in cities around a geographic point |
Get current weather openweather_api_get_current_weather | Retrieve current weather data for a location |
Get geocoding by zip openweather_api_get_geocoding_by_zip | Convert zip/post code into geographic coordinates |
Get geocoding direct openweather_api_get_geocoding_direct | Convert a location name into geographic coordinates |
Get geocoding reverse openweather_api_get_geocoding_reverse | Convert geographic coordinates into a location name |
Get station measurements openweather_api_get_station_measurements | Retrieve aggregated measurements from a weather station with minute, hour, or day granularity |
Get uv index openweather_api_get_uv_index | Retrieve current UV index for a location |
Get uv index forecast openweather_api_get_uv_index_forecast | Retrieve UV index forecast for a specific location |
Get uv index history openweather_api_get_uv_index_history | Retrieve historical UV index data for a specified location and time range |
Get weather map tile openweather_api_get_weather_map_tile | Fetch Weather Maps 2.0 tile images |
Get weather station openweather_api_get_weather_station | Get information about a specific weather station by its ID |
Get weather stations openweather_api_get_weather_stations | List all weather stations added to your account |
Get weather triggers openweather_api_get_weather_triggers | Retrieve weather triggers for specific conditions |
Get5 day forecast openweather_api_get5_day_forecast | Get a 5-day forecast every 3 hours (up to 40 UTC timestamps) |
Post add weather station openweather_api_post_add_weather_station | Add a new weather station to your account |
Post submit station measurements openweather_api_post_submit_station_measurements | Submit weather measurements from a registered station |
Update weather station openweather_api_update_weather_station | Update weather station details |
Try it: find the OpenWeather API tool you need
Browse the 20 OpenWeather API tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from OpenWeather API, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from OpenWeather API, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from OpenWeather API, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from OpenWeather API, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want OpenWeather API working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the OpenWeather API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected OpenWeather API account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for OpenWeather API. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right OpenWeather API actions to the runtime in a format your agent can reliably use. | 21 tools for OpenWeather API are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes OpenWeather API to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect OpenWeather API in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the OpenWeather API key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the OpenWeather API skill but can't call the tools
The ClawHub skill teaches OpenClaw about OpenWeather API, but the calls run through the ClawLink plugin and your connected account. Make sure OpenWeather API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect OpenWeather API from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling OpenWeather API tools
OpenWeather API tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every OpenWeather API call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
OpenWeather API returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for OpenWeather API has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw OpenWeather API integration?
Yes. ClawLink is the fastest way to connect OpenClaw to OpenWeather API: link your OpenWeather API account once in the browser and OpenClaw can call the OpenWeather API API through 21 ready-made tools — no custom code or token handling.
How do I add OpenWeather API to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink OpenWeather API skill from ClawHub, then you click Connect in the dashboard to authorize OpenWeather API. OpenClaw calls the tools from the next message — no config files, and the OpenWeather API key you paste is stored server-side instead of in your environment.
How long does it take to connect OpenWeather API to OpenClaw?
About two minutes. Sign in, click Connect next to OpenWeather API in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring OpenWeather API up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want OpenWeather API working from chat.
OpenClaw installed the OpenWeather API skill but can't call the tools
The ClawHub skill teaches OpenClaw about OpenWeather API, but the calls run through the ClawLink plugin and your connected account. Make sure OpenWeather API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
Connect SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.