Skip to main content
Glama
madhukeshm

LG Washer MCP Server

by madhukeshm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_devicesA

List all LG ThinQ devices on the account. Use this to find the washer's deviceId, which every other tool needs.

get_washer_profileA

Get a washer's capability profile: the exact controllable properties and their allowed values for THIS specific model. Consult this before controlling, because property names/values vary by model.

get_washer_statusA

Get the washer's current live state: whether it is running, the current cycle/run state, and remaining time.

control_washerA

Start, stop, power off, or wake the washer.

operation must be one of: START, STOP, POWER_OFF, WAKE_UP. location is the device zone from the profile (default "MAIN"). Location- scoped washers reject commands that omit it (API error code 2207).

Note: most LG washers only accept a remote START when the machine has been physically set to "Remote Start" and a cycle is already selected/loaded. The API pauses/resumes or starts a pre-selected cycle; it generally cannot pick a wash program from scratch. Call get_washer_profile first to confirm the model supports the operation and to see the exact accepted values.

control_washer_rawA

Escape hatch: send an arbitrary control payload to the washer.

control_json is a JSON object matching the shape shown in the device profile, e.g. {"operation": {"washerOperationMode": "START"}}. Use this for model-specific properties (timers, remote-control toggles, etc.) that the higher-level tools do not cover.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4.1/5.0

Scored across 5 tools

Disambiguation4/5

Most tools are clearly distinct: listing devices, fetching profile, fetching status, and sending commands all serve different purposes. The only mild overlap is between control_washer and control_washer_raw, but the descriptions make the intended boundary clear.

Naming Consistency5/5

All tools follow a clean snake_case verb_noun pattern: list_devices, get_washer_profile, get_washer_status, control_washer, control_washer_raw. The naming is consistent and predictable.

Tool Count5/5

Five tools is well-scoped for an LG washer MCP server: discovery, model introspection, status, high-level control, and a raw escape hatch. Each tool earns its place without adding redundancy.

Completeness4/5

The server covers the core washer workflow: find the device, inspect its capability profile, read live status, and issue commands. The raw control tool helps fill model-specific gaps, though common operations like pause/resume are not explicitly exposed beyond the raw payload path.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources