Domotz MCP

io.github.Servosity由 GitHub 账号 Servosity 发布v0.1.8更新于 Nov 7, 2026

Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions.

概览

AI 生成的概览

非官方的 Domotz MCP 服务器,让助手访问 Domotz API,并通过本地 SQLite 镜像回答跨站点网络问题。

可以做什么
  • 查询全网状态:健康度、离线设备、新出现设备、IP 冲突、未监控与未告警设备
  • 导出覆盖所有站点的统一资产清单,支持 CSV
  • 检索并查看 Domotz 数据的本地 SQLite 镜像,以及拓扑与导出
  • 按需发起实时 Domotz API 调用并同步镜像
  • 执行写入与设备控制操作,如设备编辑、标签、告警配置绑定、电源操作与删除
适用场景
适合管理多个 Domotz 站点的 MSP 与网络运维人员,让助手直接回答“哪个客户有设备掉线”“昨夜网络上出现了什么”这类全网问题,而不必逐个站点点击查看。
运行要求
以仅限桌面的本地 stdio 进程运行(.mcpb 安装包或安装脚本,同时安装配套 CLI)。需要 Domotz API 密钥(DOMOTZ_API_KEY)和正确的 DOMOTZ_REGION;仅在指向其他主机时设置 DOMOTZ_BASE_URL。多代理安装命令需要 Node.js。DOMOTZ_MCP_HTTP_TOKEN 仅用于 HTTP 传输。
安装前请注意
该服务器可写入并控制设备:编辑、告警绑定、电源与插座操作、VPN 连接、凭据与 SNMP 修改以及删除。可将 DOMOTZ_MCP_READ_ONLY 设为 1 禁止写入,先做试运行,并让破坏性或凭据类操作由人工确认。读取 SNMP 凭据会返回密钥。凭据从环境变量读取;请限制 API 密钥权限。处于 Beta 阶段,非官方,与 Domotz 公司无关联。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Domotz MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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):

Your AI agentHow to install the Domotz skill
Claude DesktopRun installer, then Settings > Extensions to register domotz-mcp (no JSON editing).
ChatGPT (desktop app)Run installer, then add domotz-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add domotz-mcp to mcp.json under the servers key, then pick Agent mode.

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.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Google GeminiGemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills 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.

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):

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

macOS / Linux:

bash
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:

bash
domotz-cli --version

Upgrade to the latest version

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

macOS / Linux:

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

Windows (PowerShell):

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 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:

bash
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):

bash
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

Question your MSP keeps askingCommand
Is anything on fire across all my sites?domotz-cli fleet health --agent
Which Collectors (sites) are offline or degraded right now?domotz-cli fleet agents --agent
What devices are offline across every client?domotz-cli fleet offline --agent
What new devices appeared on any network in the last day?domotz-cli fleet new --since 24h --agent
Give me one asset inventory across every sitedomotz-cli fleet inventory --csv
Where are IP conflicts across the fleet?domotz-cli fleet ip-conflicts --agent
Which devices can't be fully monitored (auth/SNMP gaps)?domotz-cli fleet unmonitored --agent
Which important devices could go down with nobody alerted?domotz-cli fleet unalerted --vital-only --agent
How many devices of each vendor do we manage?domotz-cli fleet breakdown --by vendor --agent

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

TierExamplesRecommended agent policy
Readfleet health, fleet offline, fleet inventory, agent device list, search, topology, exportAllow
Write (routine)agent device create-eye-snmp, agent device edit, custom-tag create, alert-profile binding bind-alert-profile-to-device, device-profile apply, importPreview with --dry-run, then a reviewed write
Physical / device controlagent device power-action-on, agent device trigger-outlet-action, agent device backup-configuration, agent connection create-agent-vpnconnectionHuman-in-the-loop; never unattended
Credential / securityagent device set-credentials, agent device set-snmpauthentication, agent device get-snmpauthentication (returns SNMP secrets), rbac create-userHuman-in-the-loop only
Destructiveagent delete, agent device delete, inventory delete, rbac delete-userHuman-in-the-loop only, explicit confirmation

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.

来源:skills/domotz/README.md,提交 62ab9f0

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

6
  1. v0.1.8最新Nov 7, 2026
  2. v0.1.7Oct 23, 2026
  3. v0.1.6Oct 23, 2026
  4. v0.1.5Oct 22, 2026
  5. v0.1.4Oct 16, 2026
  6. v0.1.3Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。