How to connect UniFi to OpenClaw
Connect UniFi to OpenClaw with ClawLink: paste your UniFi key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
UniFiAPI KEYMCPMonitor UniFi Site Manager inventory, internet health metrics, and SD-WAN configurations across the connected UI account's sites.. Once connected, OpenClaw can read and act on UniFi from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to UniFi 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 UniFi setup: install one ClawHub skill, connect UniFi in the browser, and OpenClaw can call real UniFi 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 UniFi.
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 UniFi
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with UniFi?"
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 UniFi in the ClawLink dashboard — paste your UniFi API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from UniFi, 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 UniFi is connected in the dashboard, that agent calls the same 9 UniFi tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
UniFi MCP for OpenClaw
Looking for a UniFi MCP server for OpenClaw? ClawLink connects UniFi to OpenClaw and exposes 9 UniFi tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes UniFi integration works the same way.
What the OpenClaw UniFi integration can do
9 UniFi tools are ready for OpenClaw once the account is connected.
All 9 UniFi tools for OpenClaw
| Tool | What it does |
|---|---|
Get host unifi_get_host | Get detailed information for one UniFi host by the Site Manager host ID returned by List Hosts |
Get isp metrics unifi_get_isp_metrics | Get ISP performance metrics for all accessible sites, optionally limited by a relative duration |
Get sd wan config unifi_get_sd_wan_config | Get the topology and settings of one SD-WAN configuration by ID |
Get sd wan config status unifi_get_sd_wan_config_status | Get deployment, generation, WAN, tunnel, warning, and error status for one SD-WAN configuration |
List devices unifi_list_devices | List UniFi devices managed by hosts where the connected UI account is an owner or super admin |
List hosts unifi_list_hosts | List UniFi hosts associated with the connected UI account |
List sd wan configs unifi_list_sd_wan_configs | List the SD-WAN configurations associated with the connected UI account |
List sites unifi_list_sites | List sites from UniFi Network applications associated with the connected UI account |
Query isp metrics unifi_query_isp_metrics | Get ISP performance metrics for selected host/site pairs |
Try it: find the UniFi tool you need
Browse the 9 UniFi 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 UniFi, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from UniFi, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from UniFi, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from UniFi, 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 UniFi working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the UniFi API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected UniFi 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 UniFi. | 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 UniFi actions to the runtime in a format your agent can reliably use. | 9 tools for UniFi are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes UniFi 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 UniFi in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the UniFi 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 UniFi skill but can't call the tools
The ClawHub skill teaches OpenClaw about UniFi, but the calls run through the ClawLink plugin and your connected account. Make sure UniFi 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 UniFi 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 UniFi tools
UniFi 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 UniFi 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.
UniFi 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 UniFi 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 UniFi integration?
Yes. ClawLink is the fastest way to connect OpenClaw to UniFi: link your UniFi account once in the browser and OpenClaw can call the UniFi API through 9 ready-made tools — no custom code or token handling.
How do I add UniFi to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink UniFi skill from ClawHub, then you click Connect in the dashboard to authorize UniFi. OpenClaw calls the tools from the next message — no config files, and the UniFi key you paste is stored server-side instead of in your environment.
How long does it take to connect UniFi to OpenClaw?
About two minutes. Sign in, click Connect next to UniFi in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring UniFi 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 UniFi working from chat.
OpenClaw installed the UniFi skill but can't call the tools
The ClawHub skill teaches OpenClaw about UniFi, but the calls run through the ClawLink plugin and your connected account. Make sure UniFi 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
Connect GitHub
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
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.