A MCP server as dotnet tool for the LG ThinQ Connect Smart Solutions API.

Package	NuGet
ThinQConnectApi
mcpserver.ThinQConnect

dnx mcpserver.ThinQConnect --yes

dotnet tool install --global mcpserver.ThinQConnect

• GetRoute: Resolve the ThinQ backend endpoints for the configured country.
• GetDevices: List ThinQ devices available for the configured PAT.
• GetDeviceProfile: Retrieve the profile JSON for a specific ThinQ device.
• GetDeviceProfiles: Retrieve the profile JSON for multiple ThinQ devices.
• GetDeviceState: Retrieve the current state JSON for a specific ThinQ device.
• GetDeviceStates: Retrieve the current state JSON for multiple ThinQ devices.
• ControlDevice: Send a control payload JSON to a specific ThinQ device.
• ControlDevices: Send a control payload JSON to multiple ThinQ devices.

The server reads configuration from either command-line arguments or environment variables.

• --country
• --pat
• --baseurl
• --stdio (default)
• --sse

• THINQ_COUNTRY
• THINQ_PAT
• THINQ_BASEURL

{
  "mcpServers": {
    "thinqconnect-mcp": {
      "command": "dnx",
      "args": [
        "mcpserver.ThinQConnect"
      ],
      "env": {
        "THINQ_PAT": "thinqpat_***"
      }
    }
  },
  . . .
}

• The server uses the documented ThinQ Route API to resolve the correct backend for Device API calls.
• ThinQ documents a fixed x-api-key for these APIs; this server uses that value by default.
• ControlDevice accepts raw JSON so it can pass through the device-specific control payload described by LG's device profiles.

Entity Framework Extensions and Dapper Plus are major sponsors and proud to contribute to the development of mcpserver.azuredevops.stdio.