lgtv-mcp
Related Servers
Alternatives to lgtv-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables controlling LG webOS TVs via MCP, including apps, volume, remote keys, mouse, inputs, channel selection, program guides, screenshots, and Wake-on-LAN power on, without installing additional software on the TV.395 npmMIT
- AlicenseBqualityBmaintenanceEnables agents and operators to control LG webOS TVs over a LAN through MCP, including apps, remote keys, pointer, text, power, discovery, route learning, and visual fallback.171MIT
- 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-
- AlicenseCqualityDmaintenanceAn MCP server for controlling LG webOS TVs via SSAP protocol, enabling AI clients to adjust settings, switch inputs, launch apps, and more.3715 npm1MIT
- AlicenseNot gradedqualityDmaintenanceTurns AI assistants like Claude and ChatGPT into a remote control for LG webOS smart TVs, enabling power control, volume, app launching, input switching, and more, all locally without cloud APIs.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables control of LG webOS TVs over the LAN, including reading status and picture settings, applying picture presets for consoles like PS5 and Switch 2, switching inputs, powering on/off via Wake-on-LAN, backing up and restoring settings, and showing on-screen notifications. It runs as a Streamable HTTP endpoint secured with mandatory Bearer authentication.MIT
TDQS
Scored across 18 tools
Most tools map to distinct resource+action pairs (pair_tv, power, set_volume, switch_input, launch_app, etc.), but get_status and get_tv_info have adjacent scopes (runtime state vs. hardware/network info) that could be confused. set_screen vs. power is also somewhat subtle, though the descriptions clarify the distinction.
Strong, mostly consistent snake_case verb_noun pattern (list_tvs, set_volume, switch_input, launch_app, press_keys). Minor deviations like the bare 'power' and the compound 'pair_tv_status' slightly break the pattern but remain readable.
At 18 tools the surface is on the heavier side but each tool covers a genuine capability (pairing, discovery, status, and discrete controls). Nothing feels redundant enough to remove, though the count sits near the top of the comfortable range.
Coverage is broad: pairing, discovery, status, power, volume, mute, inputs, apps, YouTube, remote keys and messages are all present. Minor gaps exist around live-TV channel control and general media playback (play/pause/stop beyond the YouTube shortcut), which agents can partly work around via press_keys.