Skip to main content
Glama
NickoScope

nickol-knx-mcp

by NickoScope
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nickol-knx-mcp

No user-submitted related servers found.

    Related Servers

    • gx3-mcp-server

      purinzan
      F
      license
      A
      quality
      A
      maintenance
      Provides 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.
      15
      45 PyPI
      5
      -

    • circuitarium-mcp

      Craftiee
      A
      license
      A
      quality
      A
      maintenance
      Local 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.
      22
      88 npm
      1
      Apache 2.0

    • SDS MCP

      salwks
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables automated project analysis and structured development specification generation. Supports multiple export formats and integrates with AI models for comprehensive project documentation and validation.
      -

    • mcp-server-kicad-tools

      rjmendez
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables automated KiCad-adjacent workflows by parsing and round-tripping S-expression files, classifying DRC/ERC reports, and generating pin-header footprints without a running KiCad instance.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 32 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources