NickoScope/nickol-knx-mcp
by Various
Design-time KNX/ETS assistant as an MCP server: validate (naming·DPT·status·Secure·Matter), repair (propose fixes), decompose devices (exact vendor models from ETS app-programs), d
MCP
NickoScope/nickol-knx-mcp
Added 13 July 2026
Overview
NickoScope/nickol-knx-mcp is a design-time KNX/ETS assistant implemented as an MCP server. It validates naming, DPT, status, Secure, and Matter configurations, proposes fixes, decomposes devices into exact vendor models from ETS app-programs, diffs versions, and generates Home Assistant YAML, ETS exports, an as-built handover pack, and KNX IoT output. It operates read-only with no live bus access.
Best for
Best for
KNX integrators and smart home developers who need automated validation and export generation during project design
Use cases
- Validate KNX project naming, DPT, and security settings before commissioning
- Generate Home Assistant YAML and ETS exports from existing ETS projects
- Diff ETS project versions and decompose devices into vendor-specific models
How to use
Install
pip install -e . Notes
NickoScope/nickol-knx-mcp is a design-time KNX/ETS assistant implemented as an MCP server. It validates naming, DPT, status, Secure, and Matter configurations, proposes fixes, decomposes devices into exact vendor models from ETS app-programs, diffs versions, and generates Home Assistant YAML, ETS exports, an as-built handover pack, and KNX IoT output. It operates read-only with no live bus access.
5 stars on GitHub. Last updated 2026-07-09. Licensed MIT.
Use cases
- Validate KNX project naming, DPT, and security settings before commissioning
- Generate Home Assistant YAML and ETS exports from existing ETS projects
- Diff ETS project versions and decompose devices into vendor-specific models
Pros
- Read-only design avoids accidental bus interference
- Supports multiple output formats including Home Assistant YAML and KNX IoT
- Open source with 5 stars and active Python codebase
Cons
- Requires MCP server setup and Python runtime
- Limited to design-time analysis; no live bus interaction
- Dependent on ETS app-program data for accurate device decomposition
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Read-only design avoids accidental bus interference
- Supports multiple output formats including Home Assistant YAML and KNX IoT
- Open source with 5 stars and active Python codebase
Cons
- Requires MCP server setup and Python runtime
- Limited to design-time analysis; no live bus interaction
- Dependent on ETS app-program data for accurate device decomposition
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.