nickol-knx MCP server

Read from the package source without running it. The installed server may list more.

• analyze_allwrite action

  Run every check and return the report summary plus all findings.

• check_device_parameters

  Find the device whose ETS **parameter** settings differ from its N identical siblings — the odd thermostat/sensor out (e.g. one thermostat with a different setpoint/hysteresis, one presence detector with a different detection time).

• check_dpt

  Detect missing, inconsistent or mismatched DPTs.

• check_energy

  Check the metering/energy domain (energy DPTs 13.x / 14.056) and suggest a per-circuit / PV / battery / EVSE structure for the HA energy dashboard.

• check_matter

  Matter-readiness lint: which controllable functions round-trip to a Matter cluster (have command + status + a decodable DPT) and which won't.

• check_missing_status

  Detect controllable GAs lacking a status/feedback counterpart.

• check_naming

  Validate naming conventions and 3-level structure.

• check_policy

  Validate the loaded project against a **Project Policy Profile** — *your* agreed rules (main-group taxonomy, naming regex, command/status exemptions), not one universal "standard". Flags GAs whose domain doesn't match the main group your policy assigns, and names that don't match your pattern. Pass `profile_path` to a YAML profile (omit to validate against the taxonomy inferred from the project it

• check_secure

  Summarise KNX Data Secure posture + the keyring handover checklist.

• check_topology

  Check topology capacity and individual-address validity (KNX Handbook).

• compose_rooms

  Compose a **new** KNX project from a list of room templates (constructor).

• decompose_device

  Expand a device into its group-address decomposition recipe.

• diff_projects

  Semantic diff between two .knxproj files (path_a = base/old, path_b = new): added / removed GAs, DPT changes, renames, security-flag changes. Read-only.

• explain_ga

  **Provenance** for one group address — why the tool classified it the way it did. Replays the classification and shows, per decision (category / kind / status pairing), the signals that fired with a **confidence tier**: authoritative (an ETS Function role) > structural (the KNX DPT) > heuristic (a name keyword). Flags **conflicts** (e.g. a GA the DPT calls `lighting` while its name says "AC") — th

• generate_ets_group_addresses

  Generate an ETS-importable Group Address export.

• generate_ha_package

  Generate a Home Assistant KNX package YAML.

• generate_handover_pack

  Generate a project handover pack (as-built deliverable for commissioning).

• generate_knx_iot

  Export a KNX IoT semantic view (Turtle/RDF) of the project's functional datapoints — a pragmatic skeleton for the IP-native model, for review.

• generate_test_protocol

  Draft a functional acceptance protocol (per function: command → expected status, pass/fail/sign-off) as Markdown. Execution is manual/on-site; this only drafts it.

• get_devices

  List devices (individual address, name, order number, manufacturer), sorted by individual address (area/line/device numerically). Same paging contract as `list_group_addresses`: `next_cursor` / `total_matched` / `returned`.

• get_topology

  Return the area/line/device topology tree.

• grade_completeness

  Grade the project: bare functional skeleton vs as-built grade — by the presence of the professional patterns (central macros, device tuning, astro/meteo, monitoring, deep metering, scenes, reserves, a debug main).

• list_device_recipes

  List the device decomposition recipes in the built-in device library.

• list_group_addresses

  List parsed group addresses with classification, in a **stable order**.

• load_ga_export

  Load an ETS group-address export (ga-export/01 XML) instead of a full .knxproj.

• load_project

  Parse a .knxproj file (read-only) and cache it for the session.

• parse_devices_from_project

  Extract exact device object models from a .knxproj / .knxprod application programs.

• project_report

  Produce the human-readable Markdown report (review before any import).

• suggest_names

  Naming hygiene suggestions (empty names, status GAs missing a status keyword).

• suggest_repairs

  Propose concrete fixes for the project's findings — repair, don't just flag.

• validate_room_template

  Validate a Room Library template against the R1 schema (report-only).

• workspace_info

  Show the confined output workspace and the safety guarantees.

• Code scan32 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 17 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

89/100

higher than 80% of 48,255 servers

Tools

32

the typical server has 7

Tools that change things

3%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

25

more than 91% of 28,688 servers

Downloads a week

46

more than 38% of 12,191 servers with a package

nickol-knx: common questions

Is nickol-knx MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the nickol-knx safety report

How do I install nickol-knx?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does nickol-knx need an API key?

No secret keys are declared. It reads 2 settings from the environment.

Is nickol-knx maintained?

The last commit was 49 days ago (2026-09-16). The latest release is v0.8.2.

How does nickol-knx compare with other MCP servers?

safety score 89/100 (higher than 80% of 48,255 servers); tools 32 (the typical server has 7); tools that change things 3% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.