nickol-knx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NICKOL_KNX_WORKSPACE | No | The workspace directory for output files | ./knx-workspace |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_projectA | Parse a .knxproj file (read-only) and cache it for the session. |
| list_group_addressesB | List parsed group addresses with classification. |
| get_devicesA | List devices: individual address, name, order number, manufacturer. |
| get_topologyB | Return the area/line/device topology tree. |
| check_namingC | Validate naming conventions and 3-level structure. |
| check_missing_statusB | Detect controllable GAs lacking a status/feedback counterpart. |
| check_dptB | Detect missing, inconsistent or mismatched DPTs. |
| suggest_repairsA | Propose concrete fixes for the project's findings — repair, don't just flag. |
| check_secureA | Summarise KNX Data Secure posture + the keyring handover checklist. Reports how many group addresses are secured vs plaintext, flags middle groups that mix secure and plaintext addresses (a function is only as secure as its weakest GA), and emits the ETS/HA keyring workflow as a checklist. Report-only — this server never touches key material. |
| analyze_allC | Run every check and return the report summary plus all findings. |
| generate_ha_packageA | Generate a Home Assistant KNX package YAML. |
| generate_ets_group_addressesA | Generate an ETS-importable Group Address export. |
| project_reportC | Produce the human-readable Markdown report (review before any import). |
| generate_handover_packA | Generate a project handover pack (as-built deliverable for commissioning). |
| decompose_deviceA | Expand a device into its group-address decomposition recipe. A KNX actuator channel is not one GA — it expands into command/status/dimming/ position/mode objects, each with its DPT. Given a device order number, type or alias (e.g. 'ZIO-MB24', 'dimmer', 'JRA/S', 'presence detector') and a channel count, returns the objects a professional wires per channel and the total GA count. Use when turning a spec/ТЗ device list into a group-address structure. |
| list_device_recipesA | List the device decomposition recipes in the built-in device library. |
| parse_devices_from_projectA | Extract exact device object models from a .knxproj / .knxprod application programs. |
| check_matterB | Matter-readiness lint: which controllable functions round-trip to a Matter cluster (have command + status + a decodable DPT) and which won't. |
| grade_completenessA | 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). |
| check_energyA | 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. |
| suggest_namesB | Naming hygiene suggestions (empty names, status GAs missing a status keyword). |
| generate_test_protocolA | 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. |
| diff_projectsA | Semantic diff between two .knxproj files (path_a = base/old, path_b = new): added / removed GAs, DPT changes, renames, security-flag changes. Read-only. |
| generate_knx_iotB | Export a KNX IoT semantic view (Turtle/RDF) of the project's functional datapoints — a pragmatic skeleton for the IP-native model, for review. |
| workspace_infoB | Show the confined output workspace and the safety guarantees. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NickoScope/nickol-knx-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server