Developer · Local MCP server
Domotz
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.WYRE-AI/domotz-mcp- Version
- 1.1.13
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-08-28
- Updated
- 2026-08-28
- Publisher
- WYRE-AI (GitHub) · 67 servers with pages here
- Website
- github.com/WYRE-AI/domotz-mcp
- Repository
- github.com/WYRE-AI/domotz-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/wyre-ai/domotz-mcp:v1.1.13 | — | stdio |
How to connect Domotz
Domotz runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/wyre-ai/domotz-mcp:v1.1.13. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e DOMOTZ_API_KEY -e DOMOTZ_API_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/domotz-mcp:v1.1.13. It reads these environment variables: DOMOTZ_API_KEY (required, secret), DOMOTZ_API_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"domotz-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"DOMOTZ_API_KEY",
"-e",
"DOMOTZ_API_URL",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-ai/domotz-mcp:v1.1.13"
],
"env": {
"DOMOTZ_API_KEY": "<secret>",
"DOMOTZ_API_URL": "<value>",
"MCP_TRANSPORT": "<value>",
"AUTH_MODE": "<value>",
"LOG_LEVEL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from WYRE-AI (GitHub)
| Server | Runs |
|---|---|
| ConnectWise ManageMCP server for ConnectWise Manage PSA — companies, tickets, projects, time entries, and more. | Local · stdio |
| CrewhuMCP server for Crewhu — customer feedback (CSAT/NPS), employee engagement, and gamification. | Local · stdio |
| Datto BCDRMCP server for Datto BCDR — appliances, agents, recovery points, screenshots, alerts. | Local · stdio |
| Datto RMMMCP server for Datto RMM — devices, alerts, sites, jobs, and audit data. | Local · stdio |
| Datto SaaS ProtectionMCP server for Datto SaaS Protection — M365/GWS backups, restores, seats. | Local · stdio |
| Dicker DataMCP server for Dicker Data's B2B partner/reseller REST API — pricing, orders, and invoices. | Local · stdio |
| DubberMCP server for Dubber: call recordings, compliance, groups/accounts/users, and Dub.Point. | Local · stdio |
| ESET PROTECTMCP server for ESET PROTECT's ESET Connect API - device, EDR, vulnerability, patch, and user data. | Local · stdio |
| FreshdeskMCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base. | Local · stdio |
| GoreloMCP server for Gorelo's PSA ticket, client, contact, contract, asset, and time-tracking APIs. | Local · stdio |
| HaloPSAMCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API. | Local · stdio |
| HuduMCP server for Hudu IT documentation — companies, assets, articles, passwords, and procedures. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Domain SecurityAudit a domain's email and web security: SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS, WHOIS. No API keys. | Local · stdio |
| Domainintel MCPDomain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains. | Local · stdio |
| Dominion ObservatoryTrust checks for MCP servers: trust scores, tool-drift detection, signed diligence receipts. Free. | Remote · HTTP |
| Dominion ObservatoryRuntime behavioral trust scoring for MCP servers. Check reliability before calling unknown tools. | Remote · SSE |
| DomotzMCP server for Domotz network monitoring — agents, devices, alerts, and network discovery. | Local · stdio |
| donovanh MCP-SERVERMCP server for Lightning Tools — pay-per-call AI tools via Bitcoin Lightning. | Local · stdio |
| DoomObsolescence-risk screening: predicts if a product gets absorbed into core LLM-platform features. | Remote · HTTP |
| Doom MCPPlay DOOM via MCP - works with Claude Code, Cursor, and any MCP client. | Local · stdio |