lgtv-control-mcp
An MCP server for controlling LG webOS TVs via SSAP protocol, enabling AI clients to adjust settings, switch inputs, launch apps, and more.
README
lgtv-control-mcp
An MCP (Model Context Protocol) server for controlling LG webOS TVs from AI clients like Claude, Codex, GitHub Copilot, and Antigravity.
Communication uses the webOS SSAP protocol over WebSocket, the same one used by the LG ThinQ app and projects like ColorControl.
Tools
set_backlight: backlight 0-100set_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)
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-mcp
This 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@latest
This 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.js
Pairing
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.
Client configuration
Set the TV's IP using the LGTV_HOST environment variable in your client config.
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@latest
If 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@latest
Or 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 |
|---|---|---|---|
LGTV_HOST |
yes | - | TV IP address on the local network |
LGTV_PORT |
no | 3001 |
3001 = wss (self-signed TLS); use 3000 for plain ws |
LGTV_CLIENT_KEY |
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"
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.
- Re-pairing: delete the TV's entry in
~/.lgtv-control-mcp/keys.jsonto force a new pairing prompt.
How it works
The server opens an SSAP WebSocket with the TV, performs the registration handshake (with pairingType: PROMPT), and sends ssap://... requests. 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.