Skip to main content
Glama

Related Servers

Alternatives to ecu-harness

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      F
      maintenance
      Enables AI assistants to search documentation, read and update configuration files, and discover settings across your development workspace. Supports JSON, YAML, TOML, and Markdown files with seamless integration for GitHub Copilot and other MCP clients.
      5
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding assistants to connect directly to SAP ABAP systems via ABAP Development Tools, so they can retrieve and manage source code for programs, classes, interfaces, functions, tables, and CDS views. Also supports RAP development, running unit tests and coverage checks, inspecting transports and version history, and working across multiple SAP systems.
      65
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and analyze Microsoft Dynamics 365 Finance & Operations artifacts, read local source code, and generate context-aware solutions through natural language.
      71 npm
      12
      -

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct role in the ECU workflow: discovery, reading, schema lookup, editing, validation, change inspection, change completion/discard, and recipes. The closest pair, ecu_validate and ecu_change_finish, are still clearly differentiated because finish additionally closes the change and writes the report.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with the ecu_ prefix, and the change-lifecycle tools use a predictable ecu_change_* convention. Verb choices are clear and uniform (overview, find, get, describe, edit, validate, diff, finish, discard, recipe).

    Tool Count5/5

    Ten tools is well-scoped for an ECU configuration harness. The set covers discovery, schema inspection, editing, validation, and atomic change lifecycle without redundant or filler tools.

    Completeness5/5

    The tool surface covers the full workflow: orient with ecu_overview, discover with ecu_find, inspect with ecu_get and ecu_describe, modify with ecu_edit, validate, inspect diffs, then finish or discard. Recipes provide procedural guidance for common tasks, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues