Log inSubmit server
Nickol Knx MCP logo

Nickol Knx MCP

by NickoScope

Design-time KNX/ETS6 assistant for auditing .knxproj files and generating validated Home Assistant and ETS project outputs.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Nickol Knx MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "nickoscope-nickol-knx-mcp": {
      "command": "uvx",
      "args": [
        "nickol-knx-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

NickoScope/nickol-knx-mcp MCP server analyzes KNX/ETS6 project files without connecting to or modifying the live KNX bus. It can design projects from specifications, audit and repair existing projects, generate Home Assistant YAML, and compose new projects from room templates. Outputs include validation findings, fix proposals, ETS XML/CSV exports, reports, acceptance protocols, and handover materials. Reach for it when you need a read-only design-time workflow for KNX project review or documentation.

Use cases

  • Audit an ETS5 or ETS6 project for naming, DPT, and command/status issues
  • Generate Home Assistant YAML from a KNX project model
  • Design a new KNX project from an equipment specification
  • Compose a room-based project with a basic or comfort preset
  • Export ETS XML/CSV and project handover documentation

Key features

  • Read-only .knxproj parsing
  • DPT, naming, and command/status validation
  • Home Assistant YAML generation
  • ETS XML/CSV export
  • Room-template project composition
  • Device-parameter consistency checks

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

16/16 checks healthy over the last 81d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · nickol-knx-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars29Stargazers on the source repository.
Last commit1mo agoMost recent push to the default branch.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Nickol Knx MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Nickol Knx MCP

No. It is read-only for design-time work and does not connect to the live KNX bus.

Yes. It can generate assembled Home Assistant entities and YAML for colour lights, climate, covers, and sensors.

Related MCP servers

All in Home Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNickol Knx MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nickoscope-nickol-knx-mcp?style=directory)](https://allmcps.com/mcp/nickoscope-nickol-knx-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/nickoscope-nickol-knx-mcp"><img src="https://allmcps.com/api/badge/nickoscope-nickol-knx-mcp?style=directory" alt="Nickol Knx MCP on AllMCPs" /></a>