Skip to main content
Glama
brunofgmag

lgtv-control-mcp

by brunofgmag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to lgtv-control-mcp

No user-submitted related servers found.

    Related Servers

    • remote-control-tv

      Hustawek
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets AI agents control Android TVs via ADB, including searching and playing content across streaming services, managing power and volume, and sending remote control commands.
      6
      1 npm
      4
      MIT

    • lg-tv-mcp

      OmerLapidot
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns 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.
      5
      MIT

    • tuya-infrared-mcp

      1124823599331l-boop
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control devices via Tuya infrared remote control, supporting actions like toggling power and setting modes through natural language.
      7
      MIT

    • lg-tv-use-mcp

      iJaack
      A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      17
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 37 tools

    Disambiguation2/5

    Several tools have overlapping functionality: send_button duplicates many specific control tools (volume_up/down, channel_up/down, set_mute, etc.), and set_backlight is a subset of set_picture_setting. This creates ambiguity for an agent selecting the appropriate tool.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern using snake_case, with get_, set_, list_, media_ prefixes. Minor inconsistency: get_picture_settings vs set_picture_setting (singular vs plural), but overall highly predictable.

    Tool Count2/5

    37 tools is excessive for a TV control server. Many tools (e.g., send_button, volume_up/down, set_volume) provide redundant ways to achieve the same result, bloating the surface and making it harder for agents to navigate.

    Completeness2/5

    The server lacks a tool to turn the TV on (only power_off exists) and does not provide a way to get the current active input. These are significant gaps for a TV control interface.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources