lg-thermav-mcp-server

LG Therma V MCP server that exposes heat-pump controls and status to MCP clients by connecting to a Therma V heat pump over Modbus TCP.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Infrastructure mcp modbus hvac home-automation iot go automation

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Security posture is largely unknown from the provided README. Likely no transport security for Modbus TCP beyond what the underlying network provides; MCP server auth/authorization is not documented. MODBUS_URL includes internal IP/port and should be treated as sensitive operational configuration. Consider network segmentation and firewalling to restrict access to the Modbus device and MCP server.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an MCP tool interface for a local Modbus TCP–connected LG Therma V heat pump and can accept early-development limitations.

Avoid When

You need strong guarantees around API stability, error handling, or hardened security controls; or you require web APIs/SDKs instead of an MCP server.

Use Cases

• Automating LG Therma V heat pump operations via an MCP-capable AI agent/client
• Creating assistant tools for reading and adjusting HVAC parameters over Modbus TCP
• Integrating home/IoT HVAC control into MCP-based workflows (e.g., Claude Desktop)

Not For

• Production-critical HVAC control without validation and safeguards (project is explicitly early/unstable)
• Environments where exposing Modbus on the network is not acceptable
• Use cases requiring standardized REST/GraphQL/SDK-based integration

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: None documented (local process configuration via environment variables/config)

OAuth: No Scopes: No

No auth mechanism is described for the MCP server itself in the provided README. Access is likely controlled by who can reach the MCP host process and who can configure MODBUS_URL.

Pricing

Free tier: No

Requires CC: No

Open-source MIT project; no pricing info provided for usage beyond running your own binary.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Project is labeled early development; tool/API behavior may change.
⚠ Must supply correct MODBUS_URL for Modbus TCP connectivity; connection issues may appear as tool failures.
⚠ Modbus-based HVAC writes can be stateful; agents should avoid repeated writes without checking current state.

Alternatives

Direct Modbus TCP integration using a Modbus client library Other HVAC/LG integrations available as mature Home Assistant components (if available for your exact model) Build an MCP server wrapper around an existing, well-maintained Modbus-to-HVAC abstraction

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for lg-thermav-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.