nickol-knx-mcp < mcp-name: io.github.NickoScope/nickol-knx-mcp A design-time KNX / ETS6 assistant exposed as an MCP server.** Four things you can do with it — all **without ever touching the live KNX bus**: 1.
claude mcp add nickol-knx-mcp -- npx -y nickol-knx-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
28 ★ · NickoScope/nickol-knx-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 28 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository NickoScope/nickol-knx-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**A design-time KNX / ETS6 assistant exposed as an MCP server.** Four things you can do with it — all **without ever touching the live KNX bus**: 1. **Design a project from a spec** — turn an equipment list / project specification into a complete, validated group-address structure **plus the full implementation document set** (ETS-importable XML/CSV, human-readable report, Home Assistant YAML, acceptance test protocol, as-built handover pack). 2. **Audit, repair & finish an existing project** — validate naming · DPT & sub-DPT · command↔status · KNX Secure · Matter-readiness, get **concrete fix proposals** (inferred DPTs, synthesised status GAs), grade completeness, and diff two project versions. 3. **Generate the smart-home layer** — assembled Home Assistant entities (colour lights, climate, covers, sensors) that read *real device state*, with everything ambiguous deferred to human review. 4. **Compose a new project from parametrised room templates** — from a list of rooms (with a basic/comfort preset per slot) assemble a **new**, validated project → an allocation manifest + ETS GA XML/CSV + a device BOM proposal. Dry-run, new projects only (**R1**). Under the hood: a **device library** that expands each actuator into its real communication objects — from generic recipes up to the **exact vendor object model** parsed straight from ETS application programs. -0b3d2e) 🇷🇺 **Русская версия:** README.ru.md --- 🎬 Explore the live interactive demo & dashboard → > **New — a whole demo house.** examples/demo-home ships a synthetic > **239-GA / 47-Function** project, the tool's generated report + Home Assistant config + ETS export, and a > full smart-home **“brain”** — circadian lighting, an **8-factor climate setpoint**, a presence/season/time > state machine and statistics — driving a **5-view dashboard**. See it all on the > **live site ↗**. --- 🖥️ The dashboard — live in Home Assistant Real screenshots from a live Home Assistant running the demo house. They show the tool's assembled entities at work: **RGBW / RGB / CCT colour lights**, **six floor-heating climate zones** (target, mode and valve %), a **circadian** lighting curve and a **computed** climate setpoint — not set by hand. | Climate | Lighting | |:---:|:---:| | | | | **Energy & stats** | **Presence** | | | | ▶ **Explore it interactively on the live site →** · config in examples/demo-home/ha-brain --- 🧪 Status & call for testers This is a **public beta**. The full pipeline passes an end-to-end smoke test on a synthetic project and has been validated against **real multi-thousand-GA ETS5/ETS6 projects** (anonymised) — but real ETS projects are wonderfully messy and diverse, and more field reports make it better. **👉 If you have an ETS5/ETS6 project, please try it and tell us what happens.** Open a Real-project test report issue. The tool is read-only and never connects to a bus, so testing is safe (see Safety model). See CONTRIBUTING.md for details. 💬 **Join the discussion →** — say hi, ask anything, or share what the tool found on your project. --- 🗺️ Roadmap — shaped by real integrators Recent reviews from practising KNX integrators (in Discussions) are steering what comes next: - **Cross-device parameter consistency** *(shipped — check_device_parameters)* — flag the one device whose ETS **parameter** settings differ from its N identical siblings: a thermostat with a different setpoint/hysteresis, a presence detector with a different detection time. Extracts per-device parameters straight from the .knxproj and finds the odd one out on real 42–275-device projects — read-only, no ETS, no bus — and correctly reports **nothing** on a clean project (no false positives across a different vendor / integrator school). - **Project Policy Profile** *(shipped — check_policy)* — validate a project against *your own* agreed rules (naming, GA taxonomy, command/status exemptions) instead of one universal "professional standard", since conventions differ per integrator; with no profile it validates against the taxonomy inferred from the project itself. - **Room Template Library** — compose a **new** project from parametrised room templates. **R1 shipped** (compose_rooms + validate_room_template: new projects, dry-run, allocation manifest + ETS XML/CSV + device BOM). **R2 planned**: docking into an existing project + exact device selection. - **Logic Machine support** *(coming — in research)* — bring the same read-only, design-time model to **Logic Machine** (Embedded Systems) installations: parse an LM-based KNX project and run the same naming / DPT / status / topology audits and produce the same handover output, so LM integrators get the same evidential project model they already get from a raw .knxproj. Currently scoping against a real Logic Machine 5 unit.