Domotz MCP
Mirror Domotz sites and devices locally so your agent can answer cross-site network monitoring questions in one thread.
Overview
Domotz MCP is a MCP server for the Operate phase that exposes every Domotz endpoint plus a local SQLite fleet mirror for cross-site monitoring questions.
What is this MCP server?
- Coverage of Domotz API endpoints exposed as MCP tools over stdio (v0.1.0).
- Local SQLite fleet mirror for cross-site questions without repeated portal navigation.
- DOMOTZ_API_KEY or DOMOTZ_PUBLIC_API_KEY plus optional DOMOTZ_REGION for API cell selection.
- Default region documented as us-east-1-cell-1 when not overridden.
- Version 0.1.0 stdio mcpb package from Servosity msp-skills releases
- Two API key env options: DOMOTZ_API_KEY or DOMOTZ_PUBLIC_API_KEY
- Optional DOMOTZ_REGION with default us-east-1-cell-1
Community signal: 1 GitHub stars.
What problem does it solve?
Checking multiple Domotz sites in the portal slows down triage when you already live inside Claude Code or Cursor.
Who is it for?
One-person MSPs and indie infra operators who rely on Domotz for LAN monitoring across several customer sites.
Skip if: Builders without a Domotz subscription who only need application-level error tracking.
What do I get? / Deliverables
After setup, your agent can query Domotz-backed tools and the SQLite mirror to compare devices and sites without leaving the chat.
- MCP tools mapped to Domotz API endpoints
- Local SQLite fleet mirror for agent queries
- Region-aware Domotz API connectivity
Recommended MCP Servers
Journey fit
Network visibility for client sites is a run-phase responsibility once you operate managed infrastructure or internal lab networks. Domotz is network discovery and monitoring; Operate → Monitoring is where agents need live and mirrored device context.
How it compares
Domotz network-monitoring MCP with a SQLite mirror—not a PSA ticket server or generic browser automation skill.
Common Questions / FAQ
Who is Domotz MCP for?
It is for solo operators and small teams that monitor client networks with Domotz and want that data available to MCP agents.
When should I use Domotz MCP?
Use it when investigating connectivity, device changes, or cross-site anomalies during ongoing monitoring and support work.
How do I add Domotz MCP to my agent?
Add the domotz-mcp mcpb v0.1.0 server with stdio transport, set DOMOTZ_API_KEY or DOMOTZ_PUBLIC_API_KEY, and optionally DOMOTZ_REGION.