Skip to main content
Glama

Related Servers

Alternatives to abap-mcp-adt

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      Not graded
      maintenance
      An MCP server that enables AI assistants to interact with SAP systems via the ABAP Development Tools (ADT) REST API. It allows users to read ABAP source code, inspect DDIC objects, and execute SQL queries directly.
      66
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects AI assistants to SAP systems via the ADT REST API, enabling read, write, syntax-check, and activation of ABAP code directly from the chat.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A local MCP server that connects to SAP ABAP systems via ADT HTTP API, enabling AI assistants to search, read, and manage ABAP objects securely without SAP GUI.
      5
      214 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for SAP ABAP development and customizing that connects directly to your SAP system via ADT REST API, enabling AI assistants to search, read, write, activate, transport, debug, and run quality checks on ABAP code, as well as manage customizing/IMG configurations with governed transport recording.
      MIT

    TDQS

    B3/5.0

    Scored across 143 tools

    Disambiguation2/5

    Many tools have overlapping purposes, especially the GetX and ReadX pairs (e.g., GetClass vs. ReadClass) which both retrieve source code with slight metadata differences. Additionally, several listing tools (GetObjectsList, GetPackageContents, GetObjectsByType) serve similar purposes, making it difficult for an agent to select the correct tool.

    Naming Consistency3/5

    Tools generally follow a VerbObject PascalCase pattern (e.g., CreateClass, DeleteTable). However, inconsistency arises with the use of both 'Get' and 'Read' for retrieval operations, and 'List' vs 'Get' for list operations (e.g., ListTransports vs GetObjectsList). This breaks a uniform naming convention.

    Tool Count1/5

    With 143 tools, the server is excessively large for an MCP server. While the domain is broad, this many tools leads to cognitive overload and difficulty in tool selection, far exceeding typical curated sets (3-15 tools) and even heavy sets (25+). Many tools are granular variants that could be consolidated.

    Completeness5/5

    The tool set covers the full lifecycle of ABAP development objects: create, read, update, delete for classes, interfaces, tables, structures, views, data elements, domains, function groups, modules, behavior definitions, service artifacts, and more. It also includes runtime analysis, transport management, search, and unit testing, leaving no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues