F
licenseNot graded
qualityC
maintenanceMCP server for controlling Somfy TaHoma devices locally via the box's API, without cloud dependency.
-
deConz MCP Server
by marcinn2
Related Servers
Alternatives to deConz MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for the entire Shelly smart-home ecosystem, enabling local-first control, automation, and energy monitoring of Shelly devices with cloud fallback.24725 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables LLMs to list, inspect, and control Zigbee devices via the Zigbee2MQTT frontend websocket API, eliminating the need for direct MQTT broker access.4MIT
- AlicenseAqualityAmaintenanceMCP server for administering a Zigbee2MQTT estate, enabling mesh health monitoring, device management, firmware updates, pairing, binding, and reporting via natural language.1769 npm31MIT
- FlicenseAqualityDmaintenanceMCP server for Sinum smarthome system, enabling device and scene management, and light toggling via natural language.42-
- AlicenseAqualityDmaintenanceMCP server for controlling Homey Pro smart home systems, offering 60+ tools for device control, flow authoring, automation, monitoring, and network diagnostics.60MIT
TDQS
B3.3/5.0
Scored across 39 tools
Disambiguation4/5
Tools are mostly organized by resource and action, so purposes are generally clear. A few overlaps exist: set_group_action can recall a scene via its scene parameter, duplicating recall_scene, and create_scene versus store_scene both capture current group state.
Naming Consistency4/5
The naming mostly follows a predictable list_/get_/create_/set_/rename_/delete_ pattern across resource types. Minor deviations like modify_group, store_scene, and recall_scene break the strict verb_noun convention but remain readable.
Tool Count2/5
39 tools is a large surface and exceeds the 25+ threshold. The set could be consolidated into generic state/action endpoints or grouped more tightly without losing capability, though the organization by resource does provide some structure.
Completeness4/5
The set covers most lifecycle operations for lights, groups, sensors, scenes, rules, schedules, and touchlink discovery. Obvious gaps are limited to gateway configuration updates and some sensor/device creation paths, but common workflows can be completed.
Maintenance
ActivityMaintained
ResponsivenessNo issues