lgtv-control-mcp
Summary: It exposes MCP tools for controlling an LG webOS TV over SSAP.
Set picture options: backlight 0–100, contrast/brightness/color, picture mode, and read picture settings.
Control audio: volume up/down, set volume 0–100, read volume/mute, mute/unmute.
Switch inputs and apps: list/switch HDMI inputs; list, launch, close apps; get foreground app.
Control channels and media: channel up/down, set/list/get channels; play/pause/stop/rewind/fast-forward.
Control power/screen: power off, screen off/on, read power state.
Send remote-control buttons, show toast notifications, enable/disable 3D mode.
Read system/software/service info and send raw SSAP requests as an escape hatch.
The README describes multi-TV naming/default management, but those tools are not present in the supplied schema.
Allows launching the Netflix app on an LG webOS TV and controlling playback.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lgtv-control-mcp Set the TV backlight to 50"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
lgtv-control-mcp
An MCP (Model Context Protocol) server for controlling LG webOS TVs from AI clients like Claude, Codex, GitHub Copilot, and Antigravity. Works with one TV or several: register each TV under a name like "Office" and target it directly, or let commands fall through to a default TV.
Communication uses the webOS SSAP protocol over WebSocket, the same one used by the LG ThinQ app and projects like ColorControl.
Tools
add_tv/remove_tv/list_tvs/set_default_tv: manage your TVs by name (see Multiple TVs)set_backlight: backlight 0-100set_peak_brightness: peak brightnessoff/low/medium/highset_picture_setting/set_picture_mode/get_picture_settings: contrast, brightness, color, and picture modeset_volume/volume_up/volume_down/get_volume/set_mutelist_inputs/set_input: switch HDMI and other inputslist_apps/launch_app/close_app/get_foreground_appchannel_up/channel_down/set_channel/list_channels/get_current_channelmedia_play/media_pause/media_stop/media_rewind/media_fast_forwardpower_off/screen_off/screen_on/get_power_stateset_3d_on/set_3d_offshow_toast: display a notification on the TVsend_button: press a remote button. Compatible names include0-9,HOME,BACK,ENTER,EXIT,UP,DOWN,LEFT,RIGHT,RED,GREEN,YELLOW,BLUE,POWER,VOLUMEUP,VOLUMEDOWN,MUTE,MENU,CC,DASH,CHANNELUP,CHANNELDOWN,LIST,AD,SAP,PROGRAM,PLAY,PAUSE,STOP,REWIND,FASTFORWARD,GUIDE,AMAZON,NETFLIX,MAGNIFIER_ZOOM,LIVE_ZOOM,3D_MODE,ASPECT_RATIO,RECENT,RECORD,SCREEN_REMOTE,MYAPPSget_system_info/get_software_info/get_service_listssap_request: send any raw SSAP command (escape hatch)
Every control tool accepts an optional tv argument with the name of the target TV. Without it, the command goes to the default TV.
Related MCP server: remote-control-tv
Requirements
Node.js 18+
An LG webOS TV powered on and on the same local network
The TV's IP address (Settings > Network)
Mobile TV On enabled (Settings > Connection > External Devices > On via Wi-Fi)
Installation
Global install
npm install -g lgtv-control-mcpThis puts the lgtv-control-mcp binary in your PATH. Use command: "lgtv-control-mcp" with no args in your client config.
Via npx (no install)
npx -y lgtv-control-mcp@latestThis does not install the package. The MCP client runs this command each time it starts the server; npm caches the package after the first download.
From source
git clone https://github.com/brunofgmag/lgtv-control-mcp.git
cd lgtv-control-mcp
npm install
npm run build
node dist/index.jsPairing
The first time you connect, the TV shows a "Connection Request" prompt on screen. Accept it with the remote.
The client key is saved automatically to ~/.lgtv-control-mcp/keys.json and reused on later connections. You don't need to configure it manually. If you want to pin a specific key, copy the value from that file into LGTV_CLIENT_KEY.
Multiple TVs
You can register any number of TVs by name, without touching config files. Just ask your AI:
"Add the TV 'Office' with IP 192.168.1.13"
"Add the TV 'Living Room' with IP 192.168.1.20"
"Which TVs do I have configured?"
"Remove the Bedroom TV"
Commands that don't name a TV go to the default TV. The first TV you add becomes the default; to change it, say something like "make the Living Room TV the default". To control a specific TV, name it in the request: "pause the Office TV" or "set the volume to 15 on the Living Room TV".
A few details worth knowing:
Adding a TV with a name that already exists updates it, so "change the Office TV's IP to 192.168.1.40" works without removing it first.
Names are matched ignoring case; "office" and "Office" are the same TV.
Each TV pairs separately. The first command sent to a new TV shows the connection prompt on that screen; accept it with that TV's remote.
The list is stored in
~/.lgtv-control-mcp/tvs.json, so it survives restarts and is shared by all your MCP clients.
If you only use one TV, you can skip all of this and set LGTV_HOST instead: when no TVs are registered, commands go to that address.
Client configuration
LGTV_HOST is optional in every example below. It gives you a working single-TV setup right away, but you can leave the env block out entirely and register your TVs by chat afterwards, for example "Add the TV 'Office' with IP 192.168.1.13" (see Multiple TVs). If both exist, registered TVs take precedence over LGTV_HOST.
Claude Desktop
Open Settings → Developer → Edit Config. This opens claude_desktop_config.json directly in your editor. Add the entry and restart the app.
{
"mcpServers": {
"lgtv-control": {
"command": "npx",
"args": ["-y", "lgtv-control-mcp@latest"],
"env": { "LGTV_HOST": "192.168.1.50" }
}
}
}If you installed globally, use "command": "lgtv-control-mcp" with "args": [].
Claude Code
The --scope user flag adds the server globally across all your projects:
claude mcp add lgtv-control --scope user --env LGTV_HOST=192.168.1.50 -- npx -y lgtv-control-mcp@latestIf you installed globally, replace npx -y lgtv-control-mcp@latest with just lgtv-control-mcp.
Or add it manually to ~/.claude/settings.json (user-level, global):
{
"mcpServers": {
"lgtv-control": {
"command": "npx",
"args": ["-y", "lgtv-control-mcp@latest"],
"env": { "LGTV_HOST": "192.168.1.50" }
}
}
}Codex CLI
Via CLI:
codex mcp add lgtv-control --env LGTV_HOST=192.168.1.50 -- npx -y lgtv-control-mcp@latestOr in ~/.codex/config.toml:
[mcp_servers."lgtv-control"]
command = "npx"
args = ["-y", "lgtv-control-mcp@latest"]
[mcp_servers."lgtv-control".env]
LGTV_HOST = "192.168.1.50"GitHub Copilot / VS Code
In .vscode/mcp.json or your user MCP settings:
{
"servers": {
"lgtv-control": {
"type": "stdio",
"command": "npx",
"args": ["-y", "lgtv-control-mcp@latest"],
"env": { "LGTV_HOST": "192.168.1.50" }
}
}
}For Copilot clients that expect the mcpServers format:
{
"mcpServers": {
"lgtv-control": {
"type": "local",
"command": "npx",
"args": ["-y", "lgtv-control-mcp@latest"],
"env": { "LGTV_HOST": "192.168.1.50" },
"tools": ["*"]
}
}
}Antigravity
{
"mcpServers": {
"lgtv-control": {
"command": "npx",
"args": ["-y", "lgtv-control-mcp@latest"],
"env": { "LGTV_HOST": "192.168.1.50" }
}
}
}Other MCP clients
Most clients that support local MCP via stdio use the same pattern:
{
"mcpServers": {
"lgtv-control": {
"command": "npx",
"args": ["-y", "lgtv-control-mcp@latest"],
"env": { "LGTV_HOST": "192.168.1.50" }
}
}
}Environment variables
Variable | Required | Default | Description |
| no | - | TV IP address; used when no TVs are registered with |
| no |
|
|
| no | - | Pairing key; obtained and saved automatically on first use |
Usage examples
Once configured, try asking your AI:
"Set the TV backlight to 30"
"Turn up the volume" / "Switch to HDMI 2"
"Open Netflix" / "Turn off the TV screen"
"Show a 'Dinner's ready' notification on the TV"
"Add the TV 'Office' with IP 192.168.1.13"
"Open YouTube on the Office TV"
"Make the Office TV the default"
Troubleshooting
"pairing timed out": accept the connection prompt on the TV screen and try again.
"could not connect": check the IP, that the TV is on and on the same network. Try
LGTV_PORT=3000.Backlight not changing: some firmware versions require the luna path. The server already tries SSAP first and falls back automatically. Also check that your current picture mode allows manual backlight adjustment.
Command reached the wrong TV: ask "which TVs do I have configured?" to see the registered TVs and the current default, then name the TV in the command or change the default.
401 insufficient permissionsonlist_appsorget_software_info: update to 1.1.1 or later and restart your MCP client so the server registers again. You don't need to pair again.Re-pairing: delete the TV's entry in
~/.lgtv-control-mcp/keys.jsonto force a new pairing prompt. If you setLGTV_CLIENT_KEY, remove it too, because it takes priority over the file.
How it works
The server opens an SSAP WebSocket with the TV, performs the registration handshake (with pairingType: PROMPT), and sends ssap://... requests. The registration uses LG's public signed manifest, the same one other webOS clients send, because get_software_info needs a valid signature on webOS 7. Remote control buttons use a separate pointer socket (getPointerInputSocket). Picture adjustments use setSystemSettings; when the direct SSAP path is rejected by the firmware, the server uses the luna trick (creating and closing an alert whose onclose points to luna://com.webos.settingsservice/setSystemSettings).
License
Available Tools
37 toolschannel_downA
Go to the previous channel.
Inputs: no named parameters.
channel_upA
Go to the next channel.
Inputs: no named parameters.
close_appC
Close an app by its id.
Inputs: appId (required).
get_current_channelB
Get the currently tuned channel.
Inputs: no named parameters.
get_foreground_appA
Get the currently foreground app.
Inputs: no named parameters.
get_picture_settingsA
Read current picture settings (backlight, contrast, brightness, color).
Inputs: no named parameters.
get_power_stateA
Read the current power state.
Inputs: no named parameters.
get_service_listA
List available SSAP services on the TV.
Inputs: no named parameters.
get_software_infoA
Get TV software / firmware information.
Inputs: no named parameters.
get_system_infoA
Get TV system information (model, etc.).
Inputs: no named parameters.
get_volumeA
Read the current volume and mute state.
Inputs: no named parameters.
launch_appA
Launch an app by its id (e.g. netflix, youtube.leanback.v4, com.webos.app.hdmi1).
Inputs: appId (required).
list_appsA
List installed apps and their launch ids.
Inputs: no named parameters.
list_channelsA
List available TV channels.
Inputs: no named parameters.
list_inputsA
List available external inputs (HDMI, etc.).
Inputs: no named parameters.
media_fast_forwardC
Send media fast-forward.
Inputs: no named parameters.
media_pauseB
Send media pause.
Inputs: no named parameters.
media_playB
Send media play.
Inputs: no named parameters.
media_rewindC
Send media rewind.
Inputs: no named parameters.
media_stopA
Send media stop.
Inputs: no named parameters.
power_offA
Turn the TV off (standby).
Inputs: no named parameters.
screen_offA
Turn off the screen while keeping the TV running.
Inputs: no named parameters.
screen_onB
Turn the screen back on.
Inputs: no named parameters.
send_buttonC
Send a remote-control button press. Common names: UP, DOWN, LEFT, RIGHT, ENTER, BACK, EXIT, HOME, MENU, INFO, MUTE, VOLUMEUP, VOLUMEDOWN, CHANNELUP, CHANNELDOWN, PLAY, PAUSE, STOP, REWIND, FASTFORWARD, RED, GREEN, YELLOW, BLUE, 0-9, DASH.
Inputs: button (required).
set_3d_offB
Disable 3D mode.
Inputs: no named parameters.
set_3d_onC
Enable 3D mode.
Inputs: no named parameters.
set_backlightA
Set the TV backlight level from 0 to 100. This is the primary brightness control for an LG webOS TV.
Inputs: value (required).
set_channelC
Tune to a channel by its channelId.
Inputs: channelId (required).
set_inputB
Switch to an external input by its id (e.g. HDMI_1).
Inputs: inputId (required).
set_muteB
Mute or unmute the TV.
Inputs: mute (required).
set_picture_modeB
Set the picture mode (e.g. cinema, normal, vivid, game, expert1, expert2, filmMaker, hdrEffect).
Inputs: mode (required).
set_picture_settingA
Set a picture setting (backlight, contrast, brightness or color) from 0 to 100.
Inputs: key (required), value (required).
set_volumeA
Set the TV volume to an absolute level from 0 to 100.
Inputs: volume (required).
show_toastB
Display a toast notification message on the TV.
Inputs: message (required).
ssap_requestA
Escape hatch: send a raw SSAP request to the TV. Provide the full uri (e.g. ssap://audio/getVolume) and an optional payload object.
Inputs: uri (required), payload.
volume_downA
Decrease the TV volume by one step.
Inputs: no named parameters.
volume_upA
Increase the TV volume by one step.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 37 tools
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.
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.
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.
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
Related MCP Connectors
Remote MCP server for AI.TV creators — delegate account operations to your AI agent over MCP.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Related MCP Servers
- FlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to control TVs on a local network through natural language commands. It currently supports Roku devices, allowing users to launch apps, manage playback, and navigate menus.51-
- AlicenseAqualityDmaintenanceAn 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.620 npm5MIT
- 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.7MIT
- AlicenseNot gradedqualityDmaintenanceAn 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.7MIT