pylips-mcp
Related Servers
Alternatives to pylips-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables controlling a Logitech Harmony Hub over its local WebSocket API, including listing activities and devices, starting activities, powering off, and sending IR commands.170 npmMIT
- AlicenseAqualityDmaintenanceEnables discovery and control of Philips Hue lighting devices via a local bridge using the CLIP v2 API, without any cloud dependency.10MIT
- AlicenseAqualityAmaintenanceControl any smart TV with natural language — play Netflix/YouTube/Spotify by name, cast URLs, scene presets, multi-room audio, and multi-TV sync. Supports LG, Samsung, Android TV, Roku.2342 PyPI48MIT
- FlicenseNot gradedqualityDmaintenanceEnables controlling smart home devices like lights, fans, air conditioners, and Android TVs through natural language commands, with persistent state and TV content search/playback via ADB.2-
- AlicenseNot gradedqualityCmaintenanceEnables discovering, pairing with, and controlling Samsung Tizen TVs on a local network.2 npmMIT
- FlicenseAqualityCmaintenanceEnables MCP clients to control Sony Bravia TVs over the local network, including power, HDMI inputs, apps, volume, and mute through the TV's JSON-RPC API.8-
TDQS
Scored across 17 tools
Most tools map cleanly to distinct TV functions such as power, volume, screen, apps, and Ambilight. However, the four Ambilight tools—especially ambilight_mode versus ambilight_color and ambilight_on/off—could cause some selection confusion.
The names are mostly consistent snake_case verb_noun style (power_on, volume_set, list_apps, send_key). Minor deviations like ambilight_color, ambilight_mode, and youtube_video are noun-style rather than verb-led, but the overall pattern remains readable.
17 tools is slightly above the ideal 3-15 range but is reasonable for a smart TV control server that covers power, volume, screen, Ambilight, apps, media, and remote input. No tool feels redundant or unnecessary.
The toolset covers the main smart-TV workflows: power management, volume control, muting, screen toggling, Ambilight control, app launching, media playback, remote key injection, and state retrieval. Missing input/source selection and current Ambilight color reading are minor gaps that can be partially worked around via send_key or get_state.