A
licenseA
qualityD
maintenanceEnables discovery and control of Philips Hue lighting devices via a local bridge using the CLIP v2 API, without any cloud dependency.
10
MIT
tuya-local-mcp
by ethanj2k
Related Servers
Alternatives to tuya-local-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables AI assistants to control Tuya/Smart Life smart home devices via tools like on/off, brightness, color, and custom commands.1071 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceEnables control of Yeelight smart lights over local LAN, supporting on/off, brightness, color, temperature, and auto discovery.-
- AlicenseNot gradedqualityCmaintenanceEnables control of Tuya smart lighting over the local home network, including reading device state, turning devices on or off by name, and switching between white and colour modes with RGB or temperature settings. Devices and credentials stay on the server and are scoped per household principal, so each caller only sees their own home's lights.MIT
- FlicenseNot gradedqualityDmaintenanceEnables control of smart lights through MQTT messaging protocol, supporting operations like turning lights on/off and adjusting brightness levels from 0-100.-
- AlicenseAqualityBmaintenanceEnables controlling smart bulbs over IP with power, brightness, and color adjustments, plus real-time state queries and a mock mode for testing.7ISC
TDQS
A4/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: enumeration of registered devices (list_devices), passive network discovery (discover_devices), reading state for one or all devices (get_status/get_all_status), and distinct control actions (power, brightness, color, color temp, raw datapoint). The get_* and set_* families are parallel but not overlapping.
Naming Consistency5/5
All tool names follow a consistent lowercase snake_case verb_noun pattern: list_devices, discover_devices, get_status, get_all_status, set_power, set_brightness, set_color, set_color_temp, set_datapoint. No mixed conventions or vague verbs.
Tool Count5/5
Nine tools is well-scoped for a Tuya local control server: two device discovery/listing, two status reads, five control operations including a raw escape hatch. Each tool earns its place without redundancy or bloat.
Completeness4/5
The surface covers the core lifecycle of interacting with local Tuya devices: discovery, listing, status reading, and common control actions. The raw set_datapoint tool fills gaps for unsupported product types. A minor gap is the lack of a tool to add discovered devices to the registry or update device metadata.
Maintenance
ActivitySlowing
ResponsivenessNo issues