{"id":"marinx-lg-thermav-mcp-server","name":"lg-thermav-mcp-server","homepage":null,"repo_url":"https://github.com/MarinX/lg-thermav-mcp-server","category":"infrastructure","subcategories":[],"tags":["mcp","modbus","hvac","home-automation","iot","go","automation"],"what_it_does":"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.","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"],"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.","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"],"af_score":43.8,"security_score":25.8,"reliability_score":18.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:20:15.085021+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["None documented (local process configuration via environment variables/config)"],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source MIT project; no pricing info provided for usage beyond running your own binary."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":43.8,"security_score":25.8,"reliability_score":18.8,"mcp_server_quality":55.0,"documentation_accuracy":50.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":0.0,"tls_enforcement":20.0,"auth_strength":10.0,"scope_granularity":10.0,"dependency_hygiene":35.0,"secret_handling":60.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":20.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}