Larnitech MCP server

Larnitech MCP

<!-- mcp-name: io.github.mpopovych-thinkhome/larnitech-mcp -->

Version 1.3.2 Beta · Changelog · MIT licensed

An MCP server that lets an AI agent read and control a Larnitech smart-home installation over the API2 protocol — lights, climate, blinds, sensors, meters.

It ships with a documented device-type reference built from live testing against real controllers, so the agent looks up how a widget actually behaves instead of guessing from key names. That matters more than it sounds: on this platform writing state: "closed" to a gate is acknowledged with success: true and then silently ignored, and several climate types drop half of any two-key write. Those traps are documented, checked before every write, and listed in this README's own safety section.

What it does

Reading — open, no configuration beyond the API key.

Understanding what came back — statuses are type-specific and occasionally not key/value at all.

Responses flag statuses that need care: an opaque hex blob, a malfunction fault code in place of a normal reading, an all-null payload from a meter that missed its poll cycle — which means no data, not zeros — or a bare state: "undefined", which is how a device that is physically offline still answers.

Watching — non-blocking, for "press the switch and tell me what moved".

A watch keeps its own connection alive, so it survives the controller's 5-minute idle timeout and can stay open across a long conversation.

Writing — off by default, two-phase, and never a single tool call.

Learning — findings survive the session.

Saving data — a snapshot is worth more than scrollback.

Files land in data//__.txt, one folder per controller — or in a folder of your own, if that installation already has a project directory holding its drawings, configs and controller backups:

python -m larnitech_mcp data-dir "Home" "/projects/home/backups"

Snapshots then sit with the rest of that site's files instead of in a separate store. list_snapshots finds both kinds.

Each is a JSON envelope — object, savedat, comment and the payload under data — so provenance travels with the file and readsnapshot hands back parsed structure rather than text to re-parse. Numbers stay numbers and null stays null, which matters here: telling "no data" apart from zero is the difference between a quiet meter and a reading of nothing.

Shortened. The full README is on GitHub.