nickol-knx-mcp
Related Servers
Alternatives to nickol-knx-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityAmaintenanceProvides read-only analysis of Mitsubishi GX Works3 PLC projects via MCP, enabling device tracing, cross-referencing, ladder inspection, linting, and report generation without modifying source projects.4157-
- AlicenseBqualityCmaintenanceEnables inspecting and comparing exported TunerStudio-style tune files and summarizing CSV logs, with firmware metadata, units, checksums, and format capabilities, without connecting to an ECU or modifying files.4MIT
- FlicenseCqualityDmaintenanceCreates, inspects, validates, and modifies Power BI Project (.pbip) folders, generating PBIR-style reports and TMDL semantic models from structured inputs.52-
- AlicenseAqualityAmaintenanceLocal electronics tools for MCP-capable assistants, enabling static analysis of CRUMB save files and Logisim-evolution projects, including net tracing, BOM building, electrical rule checks, and optional truth table generation.2279 npm1Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceEnables automated project analysis and structured development specification generation. Supports multiple export formats and integrates with AI models for comprehensive project documentation and validation.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect Ignition gateway backups, project exports and tag exports locally and turn them into an editable engineering reference and manual pack workspace. Runs over stdio so agents can explain, validate and complete the evidence-traced documents without uploading anything.Apache 2.0
TDQS
Scored across 32 tools
Tools are largely distinct due to consistent prefixes (check_*, generate_*, list_*, get_*) and targeted domains. Minor overlap exists (e.g., check_naming vs. suggest_names, analyze_all vs. project_report), but descriptions clarify boundaries.
Most names follow a verb_noun pattern with strong category prefixes. A few irregular names (analyze_all, project_report, workspace_info) break the pattern, but the overall style is predictable and readable.
32 tools is a large surface, well above the typical 3-15 range. While each tool appears justified, the count feels heavy and could be consolidated (e.g., parameterized check/generate tools), increasing cognitive load for agents.
The toolset covers the full KNX workflow: project loading, multiple analysis/check dimensions, report generation, exports, room composition, and device decomposition. Minor gaps exist (no direct write/apply fixes, no update/delete operations), but these are intentional design constraints.