# How to connect Ambee to OpenClaw (paste one key, 27 tools) > Connect Ambee to OpenClaw with ClawLink: paste your Ambee key once and 27 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ambee The usual route to Ambee 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 Ambee setup: install one ClawHub skill, connect Ambee in the browser, and OpenClaw can call real Ambee 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 Ambee. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Ambee** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect ambee # connect Ambee (browser OAuth) npx -y @useclawlink/cli actions ambee # list available actions npx -y @useclawlink/cli run ambee --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Ambee in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ambee API key once. Verify the connection by asking OpenClaw: > Use Ambee to geocode by place and walk me through the result in plain English. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Ambee is connected in the dashboard, that agent calls the same 27 Ambee tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Ambee MCP for OpenClaw Looking for a Ambee MCP server for OpenClaw? ClawLink connects Ambee to OpenClaw and exposes 27 Ambee tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Ambee integration](https://claw-link.dev/hermes/ambee) works the same way. ## What the OpenClaw Ambee integration can do 27 Ambee tools are ready for OpenClaw once the account is connected. ### All 27 Ambee tools for OpenClaw | Tool | What it does | |---|---| | **Geocode by place** `ambee_geocode_by_place` | Transform a place name or address into geographic coordinates | | **Get air quality by city** `ambee_get_air_quality_by_city` | Retrieve real-time air quality data for a specific city | | **Get air quality by country code** `ambee_get_air_quality_by_country_code` | Retrieve real-time air quality data for a specific country using a 3-letter ISO code | | **Get air quality by lat lng** `ambee_get_air_quality_by_lat_lng` | Retrieve real-time air quality data for a specific latitude and longitude | | **Get air quality by postal code** `ambee_get_air_quality_by_postal_code` | Retrieve real-time air quality data for a specific postal code and country | | **Get air quality forecast by lat lng** `ambee_get_air_quality_forecast_by_lat_lng` | Retrieve air quality forecast for a specific latitude and longitude | | **Get air quality history by lat lng** `ambee_get_air_quality_history_by_lat_lng` | Retrieve historical air quality data for a specific latitude and longitude | | **Get disasters by continent latest** `ambee_get_disasters_by_continent_latest` | Retrieve latest natural disaster data for a specific continent | | **Get disasters history** `ambee_get_disasters_history` | Retrieve global historical natural disaster data with date range filtering | | **Get disasters history by country code** `ambee_get_disasters_history_by_country_code` | Retrieve historical natural disaster data for a country by ISO country code | | **Get disasters history by lat lng** `ambee_get_disasters_history_by_lat_lng` | Retrieve historical natural disaster data for a specific location by coordinates with date range | | **Get disasters latest by country code** `ambee_get_disasters_latest_by_country_code` | Retrieve latest natural disaster data for a specific country using ISO country code | | **Get disasters latest by lat lng** `ambee_get_disasters_latest_by_lat_lng` | Retrieve latest natural disaster data (earthquakes, floods, droughts, volcanic eruptions) for a | | **Get elevation by lat lng** `ambee_get_elevation_by_lat_lng` | Retrieve elevation statistics (min, max, mean) for a specific latitude and longitude | | **Get elevation by place** `ambee_get_elevation_by_place` | Retrieve elevation statistics (minimum, maximum, and mean) for a location by place name | | **Get fire risk by lat lng** `ambee_get_fire_risk_by_lat_lng` | Retrieve fire risk forecast and Fire Weather Index (FWI) data for specific geographic | | **Get ili forecast by lat lng** `ambee_get_ili_forecast_by_lat_lng` | Retrieve up to 28-day forecast of Influenza-like Illness (ILI) risk using latitude and longitude | | **Get pollen forecast by place** `ambee_get_pollen_forecast_by_place` | Retrieve 48-hour pollen forecast for a specific location by place name | | **Get pollen history by place** `ambee_get_pollen_history_by_place` | Retrieve historical pollen data for a specific place name | | **Get pollen latest by lat lng** `ambee_get_pollen_latest_by_lat_lng` | Retrieve latest pollen data for a specific geographic location using latitude and longitude | | **Get pollen latest by place** `ambee_get_pollen_latest_by_place` | Retrieve latest pollen data for a specific place by name | | **Get weather forecast by lat lng** `ambee_get_weather_forecast_by_lat_lng` | Retrieve weather forecast for a specific latitude and longitude (up to 72 hours) | | **Get weather latest by lat lng** `ambee_get_weather_latest_by_lat_lng` | Retrieve current weather data for a specific latitude and longitude, including temperature | | **Get wildfire by lat lng** `ambee_get_wildfire_by_lat_lng` | Retrieves real-time wildfire data for a specific geographic location using latitude and | | **Get wildfire by place** `ambee_get_wildfire_by_place` | Retrieves real-time wildfire data for a specific location by place name | | **Get wildfire risk forecast by place** `ambee_get_wildfire_risk_forecast_by_place` | Retrieve wildfire risk forecast for a specific place | | **Reverse geocode by lat lng** `ambee_reverse_geocode_by_lat_lng` | Convert geographic coordinates into human-readable location data (address, place name, postal | ## Example prompts **Geocode By Place** > Use Ambee to geocode by place and walk me through the result in plain English. **Get Air Quality By City** > Pull the relevant data from Ambee, summarize it in plain English, and point out anything that needs attention. **Get Air Quality By Country Code** > Pull the relevant data from Ambee, summarize it in plain English, and point out anything that needs attention. **Get Air Quality By Lat Lng** > Pull the relevant data from Ambee, 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 Ambee working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ambee API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ambee 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 Ambee. | 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 Ambee actions to the runtime in a format your agent can reliably use. | 27 tools for Ambee are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ambee 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 Ambee in the browser, and the 27 tools above work from chat. There is no SDK and no config file, and the Ambee key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Ambee skill but can't call the tools The ClawHub skill teaches OpenClaw about Ambee, but the calls run through the ClawLink plugin and your connected account. Make sure Ambee 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 Ambee 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 Ambee tools Ambee 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 Ambee 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. ### Ambee 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 Ambee has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Ambee integration? Yes. ClawLink is the fastest way to connect OpenClaw to Ambee: link your Ambee account once in the browser and OpenClaw can call the Ambee API through 27 ready-made tools — no custom code or token handling. ### How do I add Ambee to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ambee skill from ClawHub, then you click Connect in the dashboard to authorize Ambee. OpenClaw calls the tools from the next message — no config files, and the Ambee key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ambee to OpenClaw? About two minutes. Sign in, click Connect next to Ambee in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Ambee 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 Ambee working from chat. ### OpenClaw installed the Ambee skill but can't call the tools The ClawHub skill teaches OpenClaw about Ambee, but the calls run through the ClawLink plugin and your connected account. Make sure Ambee 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 - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/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.