
Domotz MCP
io.github.ServosityPublished by GitHub account Servosityv0.1.8Updated Nov 7, 2026
Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions.
Overview
Unofficial Domotz MCP server that gives an assistant the Domotz API plus a local SQLite fleet mirror for cross-site network questions.
- What you can do
- Query fleet-wide status: health, offline devices, new devices, IP conflicts, unmonitored and unalerted devices
- Export one asset inventory across all sites, including CSV
- Search and inspect the local SQLite mirror of Domotz data, plus topology and exports
- Run live Domotz API calls and sync the mirror on demand
- Perform write and device-control actions such as device edits, tags, alert-profile bindings, power actions and deletions
- When to use it
- Useful for MSPs and network operators who manage many Domotz sites and want an assistant to answer fleet-wide questions like which client has something down or what appeared on a network overnight, instead of clicking through each site.
- Requirements
- Runs locally as a desktop-only stdio process (an .mcpb bundle or installer that also places a companion CLI). Needs a Domotz API key in DOMOTZ_API_KEY and the correct DOMOTZ_REGION; DOMOTZ_BASE_URL only to point at another host. Node.js is needed for the multi-agent install command. DOMOTZ_MCP_HTTP_TOKEN is only for HTTP transport.
Installation
In SourceWeft
- Open Domotz MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
[Domotz demo - animated preview]
▶ 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.mddirectly 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.
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
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companiondomotz-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 setDOMOTZ_CLI_PATHto 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:
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/domotz/install.ps1 | iex. Then authenticate per the README and rundomotz-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
macOS / Linux:
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:
Upgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
Windows (PowerShell):
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 and 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:
Inside a Hermes chat session:
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 theopenclaw: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):
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 is the better pick; check that your AI app is on the gateway's setup list.
Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?
Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.
Do I need to know how to code?
No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Domotz credentials once.
Is my Domotz data safe?
Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.
Do I need a special Domotz plan to use the API?
No add-on is required. You generate an API Key from the Domotz Portal under Settings > Services > API Keys on your existing account. A handful of endpoints (company areas, team moves, some RBAC) are Enterprise-plan only; everything else works on standard accounts, and the CLI returns a clear error when a plan gates an endpoint.
Will this replace my Domotz portal?
No. The portal and mobile app are built for working one site at a time and remain the place for live device interaction. This skill adds the fleet-wide rollups no single portal view does - across every Collector, from the terminal, scriptable and agent-ready.
Will this hit my Domotz API rate limits?
Cross-site questions read from the local SQLite mirror, not the live API, so a fleet inventory across 40 sites is one local query, not 40 API calls. The API is only touched on sync, on live commands, and where you explicitly pass --data-source live. A global --rate-limit flag caps request rate when you do go live.
What does it cost?
Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.
Safety model
The strongest control is the scope you grant the Domotz credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.
Status
Beta. Validated against the Domotz API surface and being validated with MSPs running it live against their own production tenant in our weekly Build Sessions. RSVP at compoundingteams.com/build-sessions.
Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).
Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-06-06.
Source: skills/domotz/README.md at commit 62ab9f0
Tools
0Version history
6- v0.1.8LatestNov 7, 2026
- v0.1.7Oct 23, 2026
- v0.1.6Oct 23, 2026
- v0.1.5Oct 22, 2026
- v0.1.4Oct 16, 2026
- v0.1.3Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.