How to connect Domotz to OpenClaw
Connect Domotz to OpenClaw with ClawLink: paste your Domotz key once and 99 tools work from chat. No MCP server to run, nothing stored on your machine.
DomotzAPI KEYMCPDomotz MCP lets agents inspect and manage authorized network-monitoring data, devices, alerts, sites, and IT operations through Domotz.. Once connected, OpenClaw can read and act on Domotz from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Domotz 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 Domotz setup: install one ClawHub skill, connect Domotz in the browser, and OpenClaw can call real Domotz actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Domotz skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Domotz" (hith3sh/domotz-mcp-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/domotz-mcp-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Domotz.
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 Domotz
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Domotz?"
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 Domotz in the ClawLink dashboard — paste your Domotz API key once.
Verify the connection by asking OpenClaw:
Use Domotz to collector discovery status 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Domotz is connected in the dashboard, that agent calls the same 99 Domotz tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Domotz MCP for OpenClaw
Looking for a Domotz MCP server for OpenClaw? ClawLink connects Domotz to OpenClaw and exposes 99 Domotz tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Domotz integration works the same way.
What the OpenClaw Domotz integration can do
99 Domotz tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 99.
30 of 99 Domotz tools for OpenClaw
| Tool | What it does |
|---|---|
Collector discovery status domotz_mcp_collector_discovery_status | Returns the discovery dashboard data for a collector, including initial discovery progress |
Collector overview domotz_mcp_collector_overview | Fetch a high-level overview of a collector including its identity, health status, software |
Compare config backup domotz_mcp_compare_config_backup | Compares two configuration backup snapshots of the same device |
Device inventory domotz_mcp_device_inventory | Returns detailed information about a single device: identity, status, capabilities, protocol |
Device performance domotz_mcp_device_performance | Fetch device performance metrics including round-trip delay, packet loss, uptime, SNMP sensor |
Get account info domotz_mcp_get_account_info | Returns identity and account context for the currently authenticated user: user ID, email |
Get audit log filters domotz_mcp_get_audit_log_filters | Return the set of values available for filtering Domotz audit logs: the operation categories |
Get collector alert rule bindings domotz_mcp_get_collector_alert_rule_bindings | List alert rules bound to a specific collector, including bindings at the collector level and |
Get collector capabilities domotz_mcp_get_collector_capabilities | Inspect what the customer's Collector can actually run |
Get collector credential coverage domotz_mcp_get_collector_credential_coverage | Collector-wide credential audit |
Get config backup entry domotz_mcp_get_config_backup_entry | Returns a single configuration backup snapshot's text for a device |
Get config backup status domotz_mcp_get_config_backup_status | Lists devices on a collector that have configuration backup ('config backup') enabled, with the |
Get create tag form domotz_mcp_get_create_tag_form | Shows an interactive form to create a new custom tag, with a name field and a color picker |
Get device alert rule bindings domotz_mcp_get_device_alert_rule_bindings | List alert rules bound to a specific device, including device-level bindings and bindings to |
Get device alerts domotz_mcp_get_device_alerts | Retrieve alert and monitoring configuration status for a specific device |
Get device credentials domotz_mcp_get_device_credentials | Per-device credential status drill-down |
Get device history domotz_mcp_get_device_history | Returns the per-device History / Event Log for a single device: the chronological stream of |
Get device interfaces domotz_mcp_get_device_interfaces | Lists the SNMP-collected interfaces on a device |
Get device metrics domotz_mcp_get_device_metrics | Fetch summarised time-series analytics for one or more named metrics on a device within a time |
Get device profile job history domotz_mcp_get_device_profile_job_history | Lists device-profile apply jobs for the account: which profile was applied, who submitted it |
Get driver catalog domotz_mcp_get_driver_catalog | Lists the account-wide catalog of drivers available for attaching and executing on devices |
Get driver template domotz_mcp_get_driver_template | Fetch a single driver template, including its full JS code body and requirement metadata |
Get interface traffic domotz_mcp_get_interface_traffic | Returns traffic counters for one or more device interfaces over a time range |
Get network configuration domotz_mcp_get_network_configuration | Fetch what a collector actually scans, to answer 'why isn't this device discovered?' |
Get organization domotz_mcp_get_organization | Get the full details of a single Organization by its internal id: name, organization_id |
Get uptime domotz_mcp_get_uptime | Returns uptime stats for a collector or device over a time range: total uptime percentage |
Inspect driver domotz_mcp_inspect_driver | Static analysis of a driver's JS against the Domotz sandbox |
List alert rules domotz_mcp_list_alert_rules | Lists alert rule definitions in the account |
List collector metrics domotz_mcp_list_collector_metrics | Enumerate the metrics available on a collector — speed-test thresholds, IP-conflict status |
List communication channels domotz_mcp_list_communication_channels | List the user's notification channels (email, webhook, Slack, etc.) |
Try it: find the Domotz tool you need
Browse the 30 Domotz tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Domotz to collector discovery status and walk me through the result in plain English.
Use Domotz to collector overview and walk me through the result in plain English.
Use Domotz to compare config backup and walk me through the result in plain English.
Use Domotz to device inventory and walk me through the result in plain English.
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 Domotz working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Domotz API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Domotz 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 Domotz. | 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 Domotz actions to the runtime in a format your agent can reliably use. | 99 tools for Domotz are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Domotz 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 Domotz in the browser, and the 99 tools above work from chat. There is no SDK and no config file, and the Domotz 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 Domotz skill but can't call the tools
The ClawHub skill teaches OpenClaw about Domotz, but the calls run through the ClawLink plugin and your connected account. Make sure Domotz 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 Domotz 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 Domotz tools
Domotz 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 Domotz 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.
Domotz 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 Domotz 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 Domotz integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Domotz: link your Domotz account once in the browser and OpenClaw can call the Domotz API through 99 ready-made tools — no custom code or token handling.
How do I add Domotz to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Domotz skill from ClawHub, then you click Connect in the dashboard to authorize Domotz. OpenClaw calls the tools from the next message — no config files, and the Domotz key you paste is stored server-side instead of in your environment.
How long does it take to connect Domotz to OpenClaw?
About two minutes. Sign in, click Connect next to Domotz in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Domotz 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 Domotz working from chat.
OpenClaw installed the Domotz skill but can't call the tools
The ClawHub skill teaches OpenClaw about Domotz, but the calls run through the ClawLink plugin and your connected account. Make sure Domotz 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
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.