zont-mcp
Related Servers
Alternatives to zont-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects AI assistants to the ZONT heating system via the official REST API. It enables users to monitor device states, control heating modes, and perform diagnostics using natural language.MIT
- AlicenseAqualityBmaintenanceEnables control and monitoring of an ADT Control / Alarm.com security system from MCP-compatible hosts, including checking system and device state, reviewing activity, and safely arming, disarming, locking, or adjusting devices through confirmation-gated actions and a local audit trail.11MIT
- AlicenseAqualityCmaintenanceEnables control of OtO Lawn smart sprinkler devices from MCP clients by listing devices, zones, schedules, weather, diagnostics, and starting or stopping watering on demand.19MIT
- AlicenseAqualityDmaintenanceMCP server for controlling StarLine car alarms via AI agents like Claude, providing read-only tools and command tools with human confirmation.8MIT
- AlicenseAqualityBmaintenanceEnables controlling Home Assistant from an MCP client, allowing users to read device states, call services, and run configuration commands via REST and WebSocket.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive a real Telegram account, exposing chats, messages, media, secret chats, admin rights, invite links, Mini Apps, and multi-account routing as callable tools.8GPL 3.0
TDQS
Scored across 12 tools
Several tools overlap in purpose: zont_load_data can fetch events while zont_raw_events is dedicated to events, and zont_update_device can change temperatures that zont_send_z3k_command also controls. The command-sending trio (set_io_port, send_custom_command, send_z3k_command) is differentiated by device type and command source, but an agent may still struggle to pick the right one without careful reading.
All tools use the zont_ prefix and snake_case, with a mostly consistent verb_noun pattern (get, list, add, delete, update, generate, download, set, send, load). The one deviation is zont_raw_events, which uses an adjective rather than a verb, but this is a minor inconsistency.
12 tools are well-scoped for a device management server covering authentication, CRUD, commands, data retrieval, and archives. Each tool earns its place without excessive granularity or missing functionality.
The surface covers the full device lifecycle: authenticate, list/add/update/delete devices, send various commands, retrieve history and events, and generate/download archives. No obvious dead ends for typical ZONT API workflows.