Domotz MCP

Domotz + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Domotz

API. Not affiliated with, endorsed by, or sponsored by Domotz Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs domotz-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion domotz-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set DOMOTZ_CLI_PATH to an existing binary). Details: #331.

Download Domotz MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Domotz release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install domotz@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Domotz Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.ps1 | iex. Then authenticate per the README and run domotz-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.sh)

The installer drops both domotz-cli (the CLI) and domotz-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

domotz-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update domotz@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/domotz --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/domotz --force

Hermes speaks MCP natively, so it can also use the domotz-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the domotz skill from https://github.com/servosity/msp-skills/tree/main/skills/domotz. The skill defines how its required CLI (domotz-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your Domotz portal):

DOMOTZ_API_KEY=<value> DOMOTZ_REGION=<value> domotz-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Domotz integrations and MCP servers proxy each question into a live, agent-scoped API call. That's fine for one device. It dies at scale, when you're asking "which of my 40 client sites has a device offline right now?" or "give me one asset inventory across every Collector for the QBR."

This skill syncs Domotz into a local SQLite mirror with full-text search. Aggregate questions become one local query: instant, offline, and the AI sees the answer, not raw pages of JSON. Compound commands like fleet health, fleet inventory, and fleet new roll up across every Collector, device, and site at once - work a stateless API wrapper can't do in one call.

The pain this closes

Network-monitoring threads on r/msp keep surfacing the same gap with per-site tools: visibility is organized one Collector at a time, but the questions you actually ask are fleet-wide. "Which client has something down?" "What appeared on a network overnight?" "Give me one asset list for the QBR." In the portal each of those means clicking through every site by hand or exporting per-site and merging spreadsheets - the data is all there, it just doesn't roll up across clients in a single view.

This skill closes that gap:

• `fleet health` - one status board across every site, so "is anything on fire?" is a single glance.
• `fleet offline` - every offline device across all sites, prioritized, instead of paginating each agent.
• `fleet new --since 24h` - a rogue-device sweep across all clients at once.
• `fleet inventory --csv` - the QBR/CMDB export for the whole fleet in one line.
• `fleet unmonitored` - auth/SNMP coverage gaps surfaced fleet-wide, so blind spots don't go silent.
• `fleet unalerted` - devices no enabled alert profile watches, VITAL first, so a device that goes down without paging anyone shows up before it matters.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way domotz-mcp runs, and shares MCP configuration with Codex (OpenAI): add domotz-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote server. If your team works there, a [hosted gateway](https://msp-skills.compoundingteams.com/answers/mcp-servers-for-msps-2026/#when-a-hosted