Nickol Knx MCP

What NickoScope/nickol-knx-mcp MCP server does

NickoScope/nickol-knx-mcp MCP server provides a design-time workflow for KNX and ETS6 projects through the Model Context Protocol. It reads .knxproj files and works on the project model rather than communicating with a running installation. The server is intended for planning, review, validation, and export tasks; it does not operate as a live KNX control or debugging interface.

A project can be created from an equipment list or specification, producing a group-address structure and related implementation documents. Existing projects can be inspected for naming issues, DPT and sub-DPT inconsistencies, command/status pairing problems, KNX Secure details, and Matter-readiness. The project can also be graded for completeness and compared with another project version.

How it works

The server parses project data and uses a device library to expand actuators into their communication objects. The library supports generic device recipes and exact vendor object models extracted from ETS application programs. Validation results can include concrete repair suggestions, such as inferred DPTs or synthesized status group addresses, while ambiguous decisions remain available for human review.

Room-template composition creates a new project from a room list and a basic or comfort preset for each slot. The documented R1 workflow is a dry run for new projects. It produces an allocation manifest, ETS group-address XML/CSV, and a proposed device bill of materials.

Tools and capabilities

The NickoScope/nickol-knx-mcp MCP server supports these documented workflows:

• Design a KNX project from a specification and generate its supporting document set.
• Audit, repair, and complete an existing ETS project without writing to the source project or bus.
• Generate Home Assistant entities for colour lights, climate, covers, and sensors using device-state-oriented configuration.
• Export Home Assistant YAML, ETS-importable XML/CSV, human-readable reports, acceptance test protocols, and as-built handover material.
• Check device-parameter consistency with check_device_parameters, including differences among otherwise similar devices.
• Apply project-specific validation rules with check_policy.
• Compose and validate room-based projects with compose_rooms and validate_room_template.

Limitations and notes

NickoScope/nickol-knx-mcp MCP server is in public beta. The project reports successful end-to-end testing on a synthetic project and validation against anonymised ETS5/ETS6 projects, but real projects may contain varied structures and conventions. The README asks users with ETS5 or ETS6 projects to report test results.

The server is explicitly read-only with respect to the live KNX system and never connects to the bus. It therefore should not be selected for live device control, commissioning, or runtime troubleshooting. The design-time layer is also separate from the official Home Assistant MCP server and the KNX integration used for live operation.

Room composition currently targets new projects and dry runs. Integration into an existing project and exact device selection are listed as future work. Logic Machine support is also described as under research rather than an available feature. The repository is licensed under MIT and requires Python 3.10 or newer according to its project badges.